Skip to main content

How to plan a feature release as a Product Owner in an Agile team?

[PLACEHOLDER]

One of the questions that are often presented to a Product Owner is “When will a feature XYZ be ready for the customer?”. In this article I will walk through the process of planning and estimating a feature release in an Agile software development process. 

Let’s assume the Agile team is working on a customer lifecycle management product. The next increment for the product is to support a new communication channel like SMS. The business stakeholders identified this feature as a key differentiator from the competitors. According to the business stakeholders the release of this feature is time sensitive and consequently they would like to know when the feature will be available for the customers. This time-to-market information will be used to plan marketing campaigns to create awareness of the feature. Therefore as a Product Owner it's very important to plan and estimate a new feature. The following three steps outlines how a product feature release can be planned and estimated: 


Step 1: Identify the user stories to complete the feature
The Product Owner and the scrum team must brainstorm the user stories to complete the feature. At the end of this process the Product Owner must have a set of clearly defined user stories in the product backlog. Given that the feature is of high priority these user stories must be stacked at the top of the prioritized product backlog. This will ensure that the Scrum team creates the Sprint backlog with the user stories related with the new feature. 

The Product Owner must also collaborate with the Scrum team to estimate the level of effort required to complete each user story. The level of effort can be captured as story points.

The screen shot below describes how the user stories related to the feature is prioritized in the product backlog.

story-backlog-flow
by Beolle.com


Step 2: Use feature release map to plan and estimate
Let’s assume the Scrum team works in a 2 week sprint and can deliver on average 15 story points per sprint (this is also known as sprint velocity).  The Product Owner can map the user stories from the prioritized product backlog as shown below to estimate the number of sprints it may take to complete the feature. The screen shot below describes how the prioritized user stories can be mapped onto future sprints to estimate the feature release. In the example below the Product Owner can estimate 3 sprints (i.e. 6 weeks) to deliver the new communication channel feature.  

sprint-points
by Beolle.com

Step 3: Maintain the feature release map
The Product Owner must update the feature release map at the end of each sprint to reflect any changes to the prioritized product backlog. This may be necessary if the scrum team discovers new information that may result in additional user stories. The Product Owner can then use the feature release map to check the status of the feature development. The feature release map can also be used to collaborate with the scrum team to identify creative approaches to meet the estimated feature release timeline.

In conclusion a feature release map is a very helpful tool for a Product Owner to plan, estimate and manage a new feature release. The map can be created using easily available tools like Microsoft Word, Visio, Lucidchart, etc. However there are dedicated tools like FeatureMap that can also be used to map user stories.


---------------------------------------------------------------------------------------------------------------------
Image credit:
The thumbnail image of this article is by Daria Nepriakhina on Unsplash

Trending posts

Demystifying OKR Scoring

You have probably read that one of the many good things about OKRs is that it provides structure and clarity to work towards common goals. It helps connect company, teams and individuals’ objectives to measurable results.   Photo by Garreth Brown via Pexels In a previous Beolle article, Herak wrote about HOSKR and OKRs. In this iteration we will focus on the OKR scoring. Measuring the “How” The KRs in OKRs are the Key Results. With them we measure the progress towards the Objectives we have set. So how do we score them in a way that makes sense, and measure the success? Few “gotchas” before we start Grades are an indication where you're going. In OKRs, scoring between .6 to .7 is your target. Scores between .8 and 1.0 are rare, meaning they are not the usual. If you find yourself completing all your OKRs within this range then something is not correct, for example, your Objectives are not Ambitious enough, meaning you always knew you (or your company or your team) were going to ach

AI with great power comes responsibility

Generative AI continues to be front and centre of all topics. Companies continue to make an effort for making sense of the technology, investing in their teams, as well as vendors/providers in order to “crack” those use cases that will give them the advantage in this competitive market, and while we are still in this phase of the “AI revolution” where things are still getting sorted.   Photo by Google DeepMind on Unsplash I bet that Uncle Ben’s advise could go beyond Peter Parker, as many of us can make use of that wisdom due to the many things that are currently happening. AI would not be the exception when using this iconic phrase from one of the best comics out there. Uncle Ben and Peter Parker - Spiderman A short list of products out there in the space of generated AI: Text to image Dall.E-2 Fotor Midjourney NightCafe Adobe Firefly

What it means to be product led

Many successful organizations including Miro, Figma, Spotify, Atlassian are using products as vehicles to drive customer acquisition and growth. These organizations use their products at the centre of their strategy to win customers and retain them.    Photo by Miguel Á. Padriñán via Pexels If you use any of these tools you are aware of the free trials and freemium versions of these products. These organizations use free versions to generate prospects, drive adoption and convert to paying customers. These organizations are always customer focused and drive to provide friction-less customer experience.  Recently I learned about the inner workings of these organizations by taking the course from Mind your Product and Pendo . Currently the course is available for free and I recommend signing up for the course while the offer is available. Please find the details at the end of the post.  I found the course very insightful and I summarized three (3) key pillars of being a product led organ

Gaming trends: What to expect

Gaming continues with an accelerated evolution and significant business growth. The incredible virtual worlds are receiving thousands of real-time players, becoming another avenue for networking, as well as entertainment. This is just impossible to ignore. The gaming industry is one of the most dynamic and innovative sectors, constantly evolving and adapting to new technologies, consumer preferences, and market opportunities. Photo by Mikhail Nilov via Pexels   Newzoo forecast the game market will grow to $217.9 billion in 2023. Newzoo 2020 Global Game Market Cloud and gaming There was a time, not too long ago, when you would buy your games and play them by inserting them into your console or computer. As more gamers demand access to high-quality games on any device, anywhere, anytime, cloud gaming will become a mainstream option for delivering games over the internet. Games are now becoming available via subscription model. An example of this is the Microsoft Xbox game pass and Xbox L

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed