Agile release planning: 7 Steps for new teams

Starting use of agile methods to deliver projects will pose challenges to any organization new to agile. Organizations that start by providing a common basis for training their teams, their subject matter experts, and senior leaders are building a foundation for success.

Even with that solid foundation of training, it can be challenging for new agile teams to develop their first release plan. The newly-trained agile project manager or scrum master may ask “where do I start”? It is important for the new team to extend their solid foundation by using the agile framework and their newly-learned practices to build their first release plan.

Application of their training in agile methods and processes will help the team extend that foundation as they build their first release plan. The help of an experienced coach will pay dividends in helping this new team get their first agile project launched successfully.

The foundation metaphor extends further. In order to perform their first release planning session, essential elements must be in place. The new agile project manager or scrum master will provide servant leadership to their team and organization by ensuring the following key preparatory steps are complete prior to the first release planning session:

Foundations of agile release planning

  • A vision – what needs to be built, and how it will provide value to customers and the organization.
  • A product owner – someone with the knowledge and passion to own the vision and to provide information and direction to ensure the team builds with that vision and value in mind.
  • A team – a dedicated cross-functional team to deliver this project.
  • A backlog – work with the product owner to create a wish list of the capabilities needed to provide the desired value.
  • Refine the backlog into user stories – the team and subject matter experts use their training to turn the wish list into user stories.
  • Prioritization – the team works with the product owner to prioritize the backlog and user stories.
  • A decision on sprint length – the team determines the length of their sprints – ideally, no longer than four weeks.
  • A rough idea of how many sprints – the team and the organization develop a rough idea (subject to ongoing refinement) of how many sprints might be necessary, or that they are willing to invest in the release, to achieve the desired outcome and value.

All of this sounds like a lot of work just to get ready to plan a release – especially coming on the heels of a multi-day investment in agile training. It is a lot of work, but it is a critical investment that is necessary to ensure the first project or release to be delivered using agile provides value to the organization. This first sprint will set the team up for success, and the first release will set the tone for successful agile transformation and use of agile on future projects.

1 2Next page

Leave a Reply

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

Back to top button