Develop Initial Release Plan

This Inception process goal describes how we will approach creating an initial plan for our team. Although the details will emerge throughout Construction, we still should think about how we’re going to work together and the general timing of that work. To be effective, we need to consider several important questions:

  • Who will be involved in planning?
  • What is the scope of our planning effort?
  • How detailed and how for how long should our plan be?
  • What cadences will the team adopt?
  • What approach to estimating will we take?

Develop Initial Release Plan

4 thoughts on “Develop Initial Release Plan

  1. Pingback: Put Practices in Context: #NoBestPractices | Disciplined Agile Delivery

  2. Pingback: Disciplined Agile Delivery » Put Practices in Context: #NoBestPractices

  3. Jan


    I’ve been reading through the documents on your website. But i cannot find an answer to a question i have.
    How would DAD respond to a potential delay (f.e. work item wrong estimated)?

    Kind regards,


  4. Scott Ambler Post author

    One of the fundamentals about estimation, or forecasting if you prefer, is that you should provide ranges. The range on an estimate should reflect the uncertainty of the information on which it is based. For example, the more uncertain your requirements (i.e. the more likely they are to evolve over time), then the bigger the range you need to provide.

    The implication is that by providing a realistic range to your estimates any updates should fall within the range. So, when you find that there are new requirements, or new understandings about existing requirements, you should still be OK.

    We cover ranged estimates in Chapter 10 of the DAD book.


Leave a Reply

Your email address will not be published. Required fields are marked *