Why do release planning

It also serves as a base to monitor progress within the project. Releases can be intermediate deliveries done during the project or the final delivery at the end. Depending on the type of project feature- or date-driven the release plan can be created in different ways:. If the project is feature-driven, the sum of all features within in a release can be divided by the expected velocity.

This will then result in the number of sprints needed to complete the requested functionality. If the project is date-driven we can simply multiply the velocity by the number of Sprints and we'll get the total work that can be completed within the given timeline.

Like the Scrum Product Backlog the Release plan is not a static plan. It will change during the whole project when new knowledge is available and e. Therefore the Release Plan should be revisited and updated in regular intervals, e. Hey, I'm Yeliz Obergfell. I'm determined to make a career grow.

My only question is, will it be yours? About Yeliz Obergfell. Hi there! It is great to meet you today. You may also be interested in:. We avoid having unfinished work, but it sometimes happens.

Jun 15, Jan 29, 19 Comments. Sep 18, 18 Comments. Jul 24, 34 Comments. Here are four reasons why. Nov 14, 31 Comments. Apr 11, 42 Comments. The discussion here is closed but join us in the Agile Mentors Community to further discuss this topic. Go to AgileMentors. It is often difficult to deliver a complex business solution in the short time frame of a single Sprint.

Sometimes extensive test periods are needed to satisfy rigorous quality requirements. Large enterprises sometimes require infrastructure changes. As Scrum no longer requires release planning, it makes no sense to require a release burndown. Scrum strives to make the process of software development and delivery transparent. A burndown can be incredibly useful in supporting this. But, there may be other ways to achieve this same objective.

By removing the guidelines on What to do, Scrum can benefit from future innovations. The Scrum Guide returns to its roots. Less can be more! But don't be fooled by 16 pages of rules; the game of Scrum is simple to understand, but difficult to master. X Login. Email address.

Not Registered? If you don't already have a Scrum. Register Here. Why do we have Release Planning? Why do we have Release Burndowns? Why has Release Planning been removed from the Scrum Guide?