concept release plan in category agile

appears as: The release pl, release plan, A release pl, release pl
Becoming Agile ...in an imperfect world

This is an excerpt from Manning's book Becoming Agile ...in an imperfect world.

The release plan provides a first pass at the work that will be created, tested, and demonstrated during the Development phase. This work is completed in iterations and queued for later deployment. Each iteration is a deliverable subset of features; these features are demonstrated at the end of development iterations.

If you work with a smaller team doing smaller projects, it may be relatively easy to create a release plan: you define the iteration length and see how many iterations will fit into the window of time allotted for the project. But as projects grow in size, complexity increases, and so does the need for coordination. Our case study is emulating a medium-size project team working on a medium-size project. We’ll stay within the medium-size context as we discuss the pieces of a release that most teams need to consider when creating their release plan.

Figure 15.1. A release plan will begin to take shape after you’ve determined your overall project window, iteration length, and time spent to prepare between iterations. Most teams need extra time at the end of a project to prepare for deployment.

15.3. Communicating the release plan with a kickoff meeting

Acme Media has involved the entire project team in creation of the release plan, so the team is up to speed on why the project is being pursued, the overall timeline, and the features assigned to each iteration. Acme still needs to bring other groups on board to make sure the project is supported and to create awareness about support that may be needed.