PRJ480 Mastering the Management of Iterative Development v2

1. PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception

2. Module 3 Objectives As a project progresses through phases and iterations, describe the changing emphasis of Project Management by: • Understanding Inception objectives, milestones, and evaluation criteria. • Understanding the basics of estimation. • Understanding principal Inception tasks and artifacts, and their uses. • Understand that the software management team must specifically determine the scope of the project.

3. Inception Primary Objectives: • Establishing the project’s software scope and boundary conditions • Determining the critical use cases of the system and the primary scenarios of operation • Demonstrating at least one candidate architecture against some of the primary scenarios • Estimating the cost and schedule for the entire project • Estimating potential risks Essential Activities: • Formulating the scope of the project • Synthesizing the architecture • Planning and preparing a business case

4. Review: Coarse-Grained Versus Fine-Grained Plans Project Plan Phase Plan Iteration Plan (current) • Phases and major milestones • What and when • Iterations for each phase • Number of iterations • Objectives • Duration • Work Breakdown Structure Iteration Plan (next) Roadmap Coarse-grained Plan Fine-grained Plans

5. Inception Considerations • Phase Focus • Project Scope/Requirements • Phase Plan • Risks • Business Case • Stakeholder Support • Development Process and Tools

6. Inception Considerations • Measurements • Progress 5% • Expenditures (rate) Low • Staffing Small team • Stability Volatile • Modularity 50%-100% • Adaptability Varying • Maturity Prototype

7. Inception Artifact Decisions In Inception, you will need to: • Decide: • Which artifacts to use in your process • How formally they will be treated • Where they fit into the lifecycle • What tools are used to author them • What roles are responsible for authoring them • Consider explicitly how to review each artifact • Refine the outline for each artifact • Decide what reports to use

8. Inception Essential Artifacts • Development Case • Vision • Risk List • Software Development Plan • Iteration Plan • Development Process • Development Infrastructure • Glossary • Use-Case Model (Outlined) Optional Artifacts • Domain Model (a.k.a. Business Analysis Model) • Prototypes

9. Artifact: Development Case • The responsibility of the Process Engineer role • Describes: • Which disciplines to use • Phases and milestones • Which artifacts to use • How to use artifacts • Which activities to perform • Additional activities • How to work in each discipline • Iteration Plan descriptions Development Case

10. Development Case Extract for Project Management BusCase.doc ItAssess.doc ItPlan.doc RiskList.doc RskMgtPln.doc SDP.doc SDP.proj StatAssess.doc

11. Development Cases Levels of Usage Informal 5-10 page overview 20 pages Typical, see the sample Development Case 100+ pages Avoid extensive Development Cases becausethey are difficult to maintain

12. Vision Vision • Outline • Product Description • Problem Statement • Stakeholders and End Users • Features • Constraints • Quality Measures Features, constraints, and a problem statement are used to gain stakeholder agreement on scope.

13. Software Development Plan Software Development Plan • Outline • Project Overview • Project Organization • Organizational Structure • External Interfaces • Roles and Responsibilities • Management Process • Project Estimates • Project, Phase, and Iteration Plans • Project Monitoring and Control • Technical Process and Supporting Process plans • Additional Plans

14. Risk List • A list of known project risks • Description • Ranking • Impacts • Indicators • Mitigation Strategy • Contingency Plan • Timing • Initial version by end of Inception • Updated per iteration Risk List

15. Other Risk-Related Artifacts Risk Management Plan Quality Assurance Plan Requirements Attributes

16. Review: RUP Effort and Time Distribution by Phase This distribution is typical for new software projects

17. Inception % Management 14 Environment/CM 10 Requirements 38 Design 19 Implementation 8 Assessment 8 Deployment 3 Total 100 RUP Distribution of Skills by Phase Percentage of effort by activity for the Inception phase.

18. Inception Evaluation Criteria • Do all stakeholders concur on the scope definition, and the cost and schedule estimates? • Are requirements understood by stakeholders? • Are the cost and schedule estimates, priorities, risks, and development processes credible? • Do the depth and breadth of an architecture prototype (if needed) demonstrate the preceding criteria? • Do you have an iteration plan for the next iteration?

19. Inception Phase Management Issues • Let’s get started, we’ll decide where to go later • Fixed-price bidding in inception

20. Inception Phase Recommendations • Quantify project risks: • Business risks • Technical risks • Development risks • Capture the vision in written form • Make sure everyone on the project reads and understands it • Don’t overstaff • Better to have few people and the right people • Maintain the appropriate level of abstraction • The focus is scope definition, not the completion of detailed requirements

21. Exercise: Collegiate Sports Case Study Refer to the Exercises section of your workbook and complete: Exercise 2: Artifact Completion Exercise 3: Work Allocation

22. Module 3 Review • The main objective of Inception is establishing the scope of the project and achieving stakeholder concurrence. • Some form of a Development Case can help you keep track of your artifact decisions for the project. • Estimation can help you plan. Time and effort can be controlled by making project adjustments that affect relevant cost factors. • Essential artifacts are: • Vision • Risk List • Software Development Plan • Iteration Plan/Assessment • Work Breakdown Structure