Chapter 5 Software Project Planning

1. Chapter 5Software Project Planning

2. Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for controlling, tracking, and monitoring a complex technical project. Why? So the end result gets done on time, with quality!

3. The Steps • Scoping—understand the problem and the work that must be done • Estimation—how much effort? how much time? • Risk—what can go wrong? how can we avoid it? what can we do about it? • Schedule—how do we allocate resources along the timeline? what are the milestones? • Control strategy—how do we control quality? how do we control change?

4. Write it Down! Project Scope Estimates Risks Schedule Control strategy Software Project Plan

5. To Understand Scope ... • Understand the customers needs • understand the business context • understand the project boundaries • understand the customer’s motivation • understand the likely paths for change • understand that ... Even when you understand, nothing is guaranteed!

6. Cost Estimation project scope must be explicitly defined task and/or functional decomposition is necessary historical measures (metrics) are very helpful at least two different techniques should be used remember that uncertainty is inherent

7. Estimation Techniques • past (similar) project experience • conventional estimation techniques • task breakdown and effort estimates • size (e.g., FP) estimates • tools (e.g., Checkpoint)

8. Functional Decomposition perform functional decomposition a Statement "grammatical of Scope parse"

9. Creating a Task Matrix Obtained from “process framework” framework activities application functions Effort required to accomplish each framework activity for each application function

10. Conventional Methods:LOC/FP Approach • compute LOC/FP using estimates of information domain values • use historical effort for the project

11. Example: LOC Approach

12. Example: FP Approach weight measurement parameter count number of user inputs 160 x 4 = 40 number of user outputs 125 x 5 = 25 number of user inquiries 48 x 4 = 12 number of files 28 x 7 = 4 number of ext.interfaces 28 x 7 = 4 algorithms 180 x 3 = 60 569 0.25 p-m / FP count-total complexity multiplier .84 478 feature points = 120 p-m

13. Tool-Based Estimation project characteristics calibration factors LOC/FP data

14. Estimation Guidelines estimate using at least two techniques get estimates from independent sources avoid over-optimism, assume difficulties you've arrived at an estimate, sleep on it adjust for the people who'll be doing the job—they have the highest impact

15. simple (0.30) simple (0.30) $380,000 $380,000 $450,000 $450,000 difficult (0.70) difficult (0.70) build build $275,000 $275,000 changes minor minor changes (0.40) (0.40) reuse reuse $310,000 $310,000 system X system X simple (0.20) simple (0.20) major major changes changes buy buy $490,000 $490,000 (0.60) (0.60) complex (0.80) complex (0.80) $210,000 $210,000 changes minor minor changes (0.70) (0.70) contract contract $400,000 $400,000 major major changes (0.30) changes (0.30) $350,000 $350,000 without changes (0.60) without changes (0.60) $500,000 $500,000 with changes (0.40) with changes (0.40) The Make-Buy Decision