Release Planning Using Agile

Just because you’re doing scrum, doesn’t mean you’re off the hook with finance and management when it comes to giving a real estimate for completion.

Scrum, as most agile processes, takes the approach that cost and time are fixed and that it’s the scope (or features) that are variable.

“You’ll rarely be remembered for missing a feature…but you’ll never be forgotten for missing a schedule”….. Which is why it’s important to make sure that communication with all stakeholders is crisp and that they understand how projects are being scheduled.

Ken Whitaker has written a detailed article on The Agile Schedule posted on article is fairly technical and includes concepts such as the “cone of uncertainty”, “rough order of magnitude”, and “definitive scheduling”.When I took the Scrum Master certification course we covered these concepts at a high level. We also talked about backlog grooming and why a good and consistent backlog grooming will do wonders for improving release scheduling. Although backlog grooming is not a formal component of the Scrum process, Ken Schwaber, who founded Scrum, advises teams to dedicate five percent of every sprint to this activity. Everyone should attend the backlog grooming meeting and help the Scrum product owner prepare the scrum backlog for the next sprint planning meeting. Activities during this meeting often include breaking epics into stories, adding stories to the backlog, clearly defining acceptance criteria and more. If this is done on a consistent basis you will greatly improve your agile release planning.

Be Sociable, Share!

Posted under Agile Methodology, Scrum

This post was written by admin on April 23, 2010

Tags: ,

1 Comment so far

  1. Renata October 17, 2015 11:51 pm

    This blog post was so helpful for me. We have a newer surtcture that has a Product Owner, Product Manager and a Design For Use engineer. All three are deeply involved in customer requirements and needs but from varying perspectives. This was a great reality check’ on who should be doing prioritizing and communicating directly with the dev teams.

Leave a Comment

Name (required)

Email (required)



More Blog Post