Forums

By posting to our forums you are agreeing to the Forum terms of use.
Release Plan
Last Post 10 Sep 2013 07:49 AM by Ian Mitchell. 2 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Sandeep Singh
New Member
New Member
Posts:6
Sandeep Singh

--
10 Sep 2013 04:09 AM
    While Going through a round of discssion i heard somewhere that, Release Plan is a low level description of Tasks. Is is true?, Because as far as Scrum Guide says Product Backlog is the only we can say milestone or items and it would be high level which continously increasing.
    Simon Reindl
    New Member
    New Member
    Posts:28
    Simon Reindl

    --
    10 Sep 2013 05:45 AM
    Hi,
    My take is that the release plan is a mechanism of communicating when the enhancements will be made to the product to the stakeholders and the team.
    It is a way of viewing the Product Backlog to forecast when the Product Backlog Items will be completed.
    Another technique to forecast feature implementation is the Product Roadmap, Roman Pichler has published a great article on road maps http://www.romanpichler.com/blog/ag...t-roadmap/

    A release plan is a tool to show other people in the organisation when you aim to implement the enhancements in to production. Sometimes the customer does not want the change at the end of every Sprint.

    Regards
    Simon
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:559
    Ian Mitchell

    --
    10 Sep 2013 07:49 AM
    > While Going through a round of discssion i heard somewhere that, Release Plan
    > is a low level description of Tasks. Is is true?

    I don't see how. Each sprint must produce a potentially releasable increment. A release plan is typically a forecast, often made on a rolling basis, of which increments actually will be released.

    I don't know the context of your discussion though. Do you have continuous integration and deployment? If so, it's possible that your releases into production are largely automated, and have (in some sense) been subsumed below task level.
    You are not authorized to post a reply.


    Feedback