What is the Scrum Release Planning Meeting, what is the Scrum Release Planning Meeting duration, and is it part of Scrum. Release planning is part of Scrum and it is required by scrum.
Estimating Scrum Tasks
A 59 Seconds Agile Video Animation
Scrum Release Planning Meeting – Part 2
A 59 Seconds Agile Article
Scrum Release Planning: Length of Sprint
The length of the sprint should be determined at the beginning of development, and typically needs to remain the constant throughout a project. This enables the Scrum Team (Scrum Master, Product Owner and Development Team) to accurately track and analyze the Sprint Velocity in order to determine the development pace.
The key to determining the length of sprints is matching granular control with the size of tasks. Developers are the best role in determining this balance. Most developers have an intuition about how long a request might take. By looking at the description of a feature, and comparing it with related features that are already completed, developers can estimate the size and complexity of the task. They may also decompose the tasks into smaller packets of work to further increase the accuracy of their estimates.
Scrum Release Planning: Release Strategies
Once the release plan is created, stakeholders know when to expect the features of a project. However, they must then decide on a release strategy. Different release strategies work for different teams, but there are two main focuses. The scrum team can either go with a functionality driven release strategy, or a date driven strategy.
Scrum Release Planning: Functionality Driven
A functionality driven release strategy focuses on getting certain features into each release. If stakeholders need certain key components quickly, they may prefer this method. Smaller and less important features may be pushed back, and take longer, but the Scrum team will get the most important features into the product and release it to the stakeholders as quickly as possible.
Scrum Release Planning: Date Driven
If stakeholders have a preference for having new features delivered regularly in a certain time frame, a date driven release strategy may be a better fit. Customers who have certain schedules in their own environment may need releases to fall into certain time windows. Perhaps this coincides with training periods or some other static time frame. In any case, these stakeholders are willing to have functionality reduced or split up, in order to meet the strict date requirements. Developers are valuable in this strategy as well, since they know how to maximize value in short release periods. If the scrum team keeps to the development pace, features should be finished just before the product is released to stakeholders.
Scrum Release Planning factors
Release planning covers a lot of factors, and developers are important in every part of the process. From creating the release plan to deciding on release strategies, the knowledge of a developer is extremely valuable. Developers know how long tasks should take, how they fit together, and how to maximize value to the stakeholders on a time frame.
User Stories Applied
A 59 Seconds Agile Book Review
User Stories Applied by Mike Cohn is one of our favourite books on Agile User Stories. The book starts with an overview into user stories, and details what a user story is and the different aspects of them. He then discusses how to go about writing a user story, and provides details of the INVEST criteria that can be used to determine if the story is meeting all of its objectives. Next Mike gives an in depth discussion of who user stories are written for and where to begin when gathering the details for them. The book then discusses acceptance testing user stories, including how to go about specifying these criteria and the responsibilities of the development team and customers during this process.
Estimating Scrum User Stories
A 59 Seconds Agile Infographic
Our Favourite Agile Books
We found these books great for finding out more information on Agile Scrum: