Chapter 7
Re-Planning of Product Releases
7.1 Introduction
Nothing in software development is as stable as change. Once release plans are created, business and stakeholder priorities might change afterward. Budgets are seldom stable, neither is the availability of human resources. Even features are evolving, and new features arrive. The once established plan is no longer valid and needs to be adjusted to the new circumstances. Planning requires permanent adjustment to change. The process to achieve this is called re-planning.
Changing features or requirements is considered one of the major causes for software product failure. A survey over 8000 projects undertaken by 350 US companies revealed that one third of the projects were never ...
Get Product Release Planning now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
