Chapter6.1

Chapter6.1 - Iterative Project Management Lifecycle...

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

View Full Document Right Arrow Icon
Iterative Project Management Lifecycle Planning Chapter 6.1 – Overall Project Planning Modified Considerably by your Instructor
Background image of page 1

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

View Full DocumentRight Arrow Icon
© 2005 Ivar Jacobson International Preface to Overall Project Planning Well into this chapter, the authors state that they had a number of reservations about including this chapter. They particularly did NOT want to give the impression that an entire project can be planned up front before any iterations take place. They assert that one must balance high-level life-cycle planning with low-level execution of the iterations.
Background image of page 2
© 2005 Ivar Jacobson International Preface to Overall Project Planning Planning is essential at various levels , but one must not obsess too much about where you are going to end up – you are unlikely to go anywhere. Unfortunately, while much of the material might appear to be common sense, people under pressure to deliver frequently lose common sense in planning and ignore several of the sacred principles. Plan well, Plan carefully, and Trust your plans…
Background image of page 3

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

View Full DocumentRight Arrow Icon
© 2005 Ivar Jacobson International Introductory Remarks – Overall Project Plan Overall project plan Should be lightweight plan Should summarize long-term direction for the project Should identify major releases to be produced Should identify business benefits to be realized. Should be simple , Should ensure project is in synch with the organization, Should enable project integration with any strategic or higher-level program management plans, and Should provide the context for successful iterative development of the software products.
Background image of page 4
© 2005 Ivar Jacobson International Initial Questions Important initial questions re: Overall Project Plan: Single or multiple releases ? When are specific business capabilities needed? Can some requirements be delayed to deliver others early? What are the latest date decisions can be made without impeding the business? How can work be organized to accomplished all this with time and resources provided?
Background image of page 5

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

View Full DocumentRight Arrow Icon
© 2005 Ivar Jacobson International Initial Questions So we develop a ‘ project roadmap .’ An overview of all major releases , goals, major requirements and risks and strategy for how and when you will make critical decisions. If several major releases, then ‘ development projects will drive all this in the form of ‘evolutions.’ Major releases will evolve into the overall software solution.
Background image of page 6
© 2005 Ivar Jacobson International Evolution and Release Planning Most significant question is, ‘What is the release strategy?’ How often? How significant of a release? Most projects plan major releases along with provisions for additional ‘ point releases ’ that address smaller issues (quality, smaller / minor enhancements). Large number of deliveries? Likely not tolerable by the
Background image of page 7

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

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 21

Chapter6.1 - Iterative Project Management Lifecycle...

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

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