Chapter4

Chapter4 - Iterative Project Management Lifecycle Planning...

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

View Full Document Right Arrow Icon
Iterative Project Management Lifecycle Planning Chapter 4 – Selected Sections Are you Ready for Iterative Project Management? pp 123-131; 142-153
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 2 Iterative Project Management / 03 - Lifecycle Planning I. Introduction There are many problems with adapting to an iterative / incremental development approach that people perceive. We will discuss several of the key issues. Right Attitude : In truth, much of the transition requires the team to have the right attitude toward the projects and how to work together . R eal change in mind-set must be accommodated Willingness to eschew the conventional methods.
Background image of page 2
© 2005 Ivar Jacobson International 3 Iterative Project Management / 03 - Lifecycle Planning Attitude is Critical! Attitude is the Real Key! New attitudes are needed. Must Address Uncertainty and Change Best way: clearly demonstrate real progress; Best shown : working software that provides real value . Verified; testaments… Must deliver immediate and realizable value back to the business Must address our attitude regarding teamwork and accountability • Will be interacting with many stakeholders continuously ; shared responsibilities, etc. Must adopt a progressive attitude – a real change in estimating, planning, and managing the software project The right team attitude is critically important!
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 4 Iterative Project Management / 03 - Lifecycle Planning Value Delivery – The Key to Success It is absolutely essential to produce real business value We must realize: Requirements are not all equal. Value working components vice technical components (like a sort) Delivering requirements with verified code might not be delivering the best business value Don’t worry about implementing lots of requirements at the expense of not focusing on real desired outcomes. Track stakeholder and business value , not project cost and schedule It is all about delivering verified, measurable Business Value!
Background image of page 4
© 2005 Ivar Jacobson International 5 Iterative Project Management / 03 - Lifecycle Planning Quick failure recipes : Requirements  Business Solution Implementing requirements versus solving problems. Problems are of a higher order… will include meeting requirements Iterative / incremental projects can fail too if developers concentrate on implementing requirements rather than iteratively solving problems . Addressing technical risk which is fine - without concomitant business value. Iterative projects can fail if developers concentrate on addressing technical risks and yet fail to deliver usable versions of software that provide realizable benefit .
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 6 Iterative Project Management / 03 - Lifecycle Planning Value Delivery – The Key to Success – slide 2 Great Statistics: Research indicates only two-thirds of implemented features in
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 / 22

Chapter4 - Iterative Project Management Lifecycle Planning...

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