Chapter2b.rr

Chapter2b.rr - Iterative Project Management Chapter 2 How...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon
07/29/11 1 Iterative Project Management Chapter 2 – How Do Iterative Projects Function? Part 2 Iterative Project Management / 01 - Iterative and Incremental
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2 Key Characteristics of a Successful Iterative Project Demonstrable, objectively measured progress Incrementally increasing functionality Continually improving quality Continual risk reduction Increasingly accurate estimates Reducing levels of change Convergence on a accurate business solution Let’s look at some of these… On time, on budget, meeting the customer’s real needs. 07/29/11 9 Iterative Project Management / 01 - Iterative and Incremental
Background image of page 2
3 1. Demonstrable, Objectively-Measured Progress Lots of ways: From book: Number of products / documents produced Number of LOC produced Number of activities completed Amount of budget consumed Amount of schedule consumed Number of requirements verified to have been implemented correctly. Best one by far: number of requirements verified to have been implemented correctly Others are indirect and may not measure real progress. But we must test the release and we must record the amount of verified software! Nice graphs in book re: requirements verified vs project schedule 07/29/11 Iterative Project Management / 01 - Iterative and Incremental 10
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
4 Demonstrable, Objectively Measured Progress Project Schedule / Iterations Requirements Verified 0% 100% 07/29/11 11 Iterative Project Management / 01 - Iterative and Incremental Development
Background image of page 4
5 Avoid Feature Creep Feature Creep is natural and practically unavoidable. Frankly, if the number of requirements grows, team will not make schedule. Solution 1 : Just say no. Will keep you on schedule, but will create ill-will and will likely result in escalation. Often unforeseen features are ‘essential’ Solution 2 : Prioritize them and negotiate with Customer What can be removed from a features list if the delivery date and resources remains constant – that is, trade? Be careful of ‘added resources!!!!!’ Best to discuss this at iteration end when plans for the next iteration are being firmed up. Underlying theme : have frequent deliverables and value present to the business sooner rather than later. Do not recommend extending the current project. Have more critical / core functions in earlier iterations 07/29/11 Iterative Project Management / 01 - Iterative and Incremental 12
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
6 2. Incrementally Increasing Functionality Essential that each iteration produce more verified, demonstratable functionality without compromising sacrificing quality established in previous iterations . But we have issues: “All iterations are not equal” 1. Amount of Effort may have been less during a previous iteration (time off; illness…) 2. Team productivity : As we progress through the iterations, we typically increase the productivity as the architecture becomes more stable, team members
Background image of page 6
Image of page 7
This is the end of the preview. Sign up to access the rest of the document.

This document was uploaded on 07/29/2011.

Page1 / 32

Chapter2b.rr - Iterative Project Management Chapter 2 How...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online