1 / 16

Software SYSTEMS DEVELOPMENT

Software SYSTEMS DEVELOPMENT. 4: System Design. Simplified view on software product development process. Project Lifecycle. Project Time Management. Activity Definition Activity Sequencing Activity Duration Estimation Schedule Development Schedule Control.

carsyn
Download Presentation

Software SYSTEMS DEVELOPMENT

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software SYSTEMS DEVELOPMENT 4: System Design

  2. Simplified view on software product development process

  3. Project Lifecycle

  4. Project Time Management • Activity Definition • Activity Sequencing • Activity Duration Estimation • Schedule Development • Schedule Control

  5. Activity DefinitionWork Breakdown Structure(WBS)

  6. Resource Allocation

  7. Duration Estimation 3 points method • a= the best-case estimate • m = the most likely estimate • b = the worst-case estimate • E = (a + 4m + b) / 6

  8. Activity Sequencing Precedence Diagram Method(PDM)

  9. Schedule DevelopmentGantt Chart

  10. Schedule Control PV=BCWS - Budgeted Cost of Work Scheduled AC=ACWP - Actual Cost of Work Performed EV=BCWP - Budgeted Cost of Work Performed • In time units: • PV = Planned Work Time for Planned Work • AC = Time Actually Spent • EV = Planned Work Time for Work Done

  11. Some Derived Metrics • SV: Schedule Variance (BCWP-BCWS) • A comparison of amount of work performed during a given period of time to what was scheduled to be performed. • A negative variance means the project is behind schedule • CV: Cost Variance (BCWP-ACWP) • A comparison of the budgeted cost of work performed with actual cost. • A negative variance means the project is over budget.

  12. Some More Derived Metrics • SPI: Schedule Performance Index • SPI=BCWP/BCWS • SPI<1 means project is behind schedule • CPI: Cost Performance Index • CPI= BCWP/ACWP • CPI<1 means project is over budget • CSI: Cost Schedule Index (CSI=CPI x SPI) The further CSI is from 1.0, the less likely project recovery becomes.

  13. SoW: Statement of Work • Deliverables: What will be delivered? • Brief description (source: SRS) • Activities: What should be done? • Brief Description (source: WBS) • Timeline: When it will be done (Milestones)? • Milestones Dates (source Gantt)

  14. Assignment: Project Plan • Project Management Team vs. Development Team • Customer plays PM role • Jointly define the scope with development team • WBS • Stop when work package can be reliably estimated • Don’t forget non-coding activities (testing, bug fixing) • Gantt Chart • Milestones/Deliverables each week • Dependencies, time and resource allocation • SoW • 2 page brief • Project/Milestones scope

  15. Weekly reports by PM team • Each week after the project kickoff • PM team: project status and metrics (10 minutes) • Development team: milestone demo (10 minutes) • Project Start Date: 23/05/2010 • Duration: 4 weeks • Reduce scope if needed.

More Related