Proper project planning is key to the success of the agile project
Adjusting to change over following a plan is a core agile value. This means that although there must be a planning to communicate a common view on how the project will evolve in the future, there must be no hesitation to change the plans upon a change required by the business
The planning should allow for improvement activities and all agile meetings.
The project planning must contain all the work related to the project, this includes work of the agile teams but also work of 3rd party suppliers
The levels for Planning are typified as follows:
Please find the checkpoints below.
|1. Both project planning and project budget are defined
2. All teams are involved in project planning
3. The release planning includes 3rd party dependencies
|1. BA techniques for release planning are used (eg. story map)
2. The release planning considers team meetings and department overhead
3. The release planning considers capacity required for team improvement activities
4. Product releases are managed to ensure a working release within the agreed time box
|1. The release planning is flexible (eg. rolling forecast)
2. The release planning considers operations
3. Planning is independent from and resilient to 3rd party dependencies, this includes backwards compatibility