This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
ProductGoals Defined. The Scrum Guide released in November 2020 states that “the productgoal describes a future state of the product … [It] is the long-term objective for the Scrum team.” It also suggests that “the productgoal is in the product backlog. Figure 1: The ProductGoal in Context.
Listen to the audio version of this article: [link] What is a Portfolio Roadmap and Do You Need One? Neither is a singular atomic product. Microsoft 365 is a product portfolio, a suite that contains productivity tools like Word, PowerPoint, and Excel. This is where product portfolio roadmaps come in. [2]
1 The ProductRoadmap is a Feature-based Plan. Traditional productroadmaps are usually output-focussed plans that map a list of features, like registration, search, and reporting, onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. I don’t think so.
Listen to the audio version of this article: [link] Overview The GO ProductRoadmap consists of five elements, as the image below shows: Date, name, goal, features, and metrics. The most important element is the goal: It describes the outcome you want to achieve or the benefit you want to provide.
The objective is the goal, which describes what you want to achieve. The key results state the specific criteria that have to be fulfilled to meet the objective. To make this more concrete, let’s look at an example: Objective : Grow the product management team. Key result 1 : Three product managers are hired.
Be clear on the reason why the meeting is needed. What’s the meeting about? For example, a product strategy workshop might have the objective to identify the key changes required to achieve product-market fit. Carefully consider who should participate in the meeting to achieve the objective you have set.
Goal-oriented (a.k.a. Traditionally, productroadmaps are output-focussed plans that map features like registration, search, and reporting onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. Listen to this article: [link]. Outcome-based).
Listen to the audio version of this article: [link] Traditional vs Outcome-based Roadmaps Before I share the four steps, let me briefly describe the main differences between a traditional, feature- and an outcome-based productroadmap. A traditional roadmap is essentially a list of features, which are mapped onto a timeline.
ProductGoals Defined. The Scrum Guide released in November 2020 states that “the productgoal describes a future state of the product … [It] is the long-term objective for the Scrum team.” It also suggests that “the productgoal is in the product backlog. Figure 1: The ProductGoal in Context.
Based on this insight, I have come up with the product strategy cycle shown in the picture below. It’s a model of an iterative process that systematically links the product strategy with the productroadmap , the product backlog , the development work, and the key performance indicators (KPIs).
This includes a sound understanding of the market, the user and customer needs, and the competition as well as solid product management skills such as the ability to develop an effective product strategy and an actionable productroadmap (as I explain in more detail in the article The T-Shaped Product Professional ).
There is no point in worrying about the product details and writing user stories if a sound product strategy is missing. But what exactly is a product strategy? How does it differ from a productroadmap and how do the two plans relate? And what’s their relationship to the product vision and the product backlog?
To successfully manage your product and maximise value delivery, you should use additional artefacts including the following five: An inspiring vision that describes the ultimate reason for offering the product; A validated product strategy that captures your approach to realise the vision and make the product successful.
Third and most importantly, focus the backlog on a specific productgoal. Then decline and remove items that do not serve this goal, as I discuss below. The Product Backlog is Too Detailed. The former means that there is no productgoal that guides the decision if an item should be added to the product backlog or not.
.” (Note that I have chosen a dual goal that captures the desired business and user benefits.). I like to take this idea further, derive several productgoals from the product strategy for the next 12 months, and capture them on a productroadmap.
Meet Ellen Brandenberger , a product coach and consultant and Director of Product at Stack Overflow. We’re excited to share that we’ve added yet another instructor to the Product Talk roster. Meet Ellen Brandenberger, a product coach and consultant and Director of Product at Stack Overflow.
To select the right KPIs, I recommend taking the following three steps: First, use the user and business goals in the product strategy to select an initial set of indicators. Then take into account the productgoals on the productroadmap to discover additional KPIs. Step 3: Add Health Indicators.
Goal-oriented (a.k.a. Traditionally, productroadmaps are output-focussed plans that map features like registration, search, and reporting onto a timeline. Such a roadmap essentially states when a piece of functionality will be delivered. Listen to this article: [link]. Outcome-based).
You need the stakeholders’ active contribution to progress the product and reach the productgoals. As the Scrum product owner, you should therefore establish close and trustful connections with the key stakeholders, collaborate with them, and involve them in important product decisions on a regular basis.
Because market awareness drives roadmaps that have the highest likelihood of “changing the game”. You’ll learn things that change your roadmaps for the better. You’ll learn things that confirm your roadmap is right. You’ll learn things that have no impact on your roadmap.
Myth #3: The product owner is responsible for the team performance. An agile development team does a good job if the memebers can reliably meet the agreed goals and create software that offers a great user experience and exhibit the desired quality. This has created more confusion and increased the misconceptions of the role.
Collaboratively set goals , for example, user and business goals on the product strategy and productgoals on the productroadmap. Involve the Stakeholders in Important Product Decisions. But this also means holding people accountable for meeting their agreements.
Organisational change and empowerment : Work with senior management, HR, and other business groups to implement the necessary organisational changes required to fully empower product people and leverage agile practises. Meetings : Prepare and facilitate meetings. The same is true for setting productgoals.
You can think of it as the approach chosen to realise the vision and achieve product success, as the following picture shows. How do I Create an Inspiring Product Vision? Second, when your product has been offered for a number of years, you might find that adjusting the product vision is helpful to keep it fresh and meaningful.
This second post on the methods we use at Onfido to help us think commercially and strategically looks at State of Productmeetings. This meeting is an exercise in strategy, an opportunity to take stock of where your product is, where it fits within the wider market, and where it should go. ProductRoadmap.
Setting smart productgoals is a vital skill for any sensible SaaS owner or product manager to get right. In this article, we’re going to explore what makes an effective productgoal, the difference between goals and product initiatives, how to set them and make them work with your product backlog, and more.
Then use the goal to focus your product backlog: Remove all backlog items that do not help meet the goal. While this approach may sound radical, it ensures that your product backlog is concise and focused. Otherwise, the roadmap will become overly detailed and volatile. Hide the Details.
For instance, the marketing strategy, the user experience (UX) design and technology choices have to align to successfully acquire new users, increase conversion, or meet another productgoal. Becoming a t-shaped product professional and using a learning roadmap to develop your skills will help you with this.
Consequently, a product manager and a Scrum product owner are leaders, too. They guide the stakeholders , development teams, and in the case of large products, other product people, to meet the agreed productgoals , create the desired outcomes, and achieve product success, as Figure 1 shows.
In practical terms, involve stakeholders and dev teams in decisions that affect the product strategy and the productroadmap —be it that you create the plans or that you make bigger changes to them. Additionally, include the development team members in product backlog decisions , and always choose sprint goals together.
Consider These Product “Owner” Teams Effective product owners need to collaborate with several kinds of teams: They work with “their” feature/product team, to write stories and create good backlogs for the near-term work. See the roadmap series. So the product owner works alone.
The Daily Scrum meeting, sometimes also referred to as stand-up meeting, wants to help the development team manage its work. In Scrum, the team collectively agrees to a sprint goal and is responsible for meeting it. The Daily Scrum is meant to be a quick meeting that lasts no more than 15 minutes.
To select the right KPIs, I recommend taking the following three steps: First, use the user and business goals in the product strategy to select an initial set of indicators. Then take into account the productgoals on the productroadmap to discover additional KPIs. Step 3: Add Health Indicators.
As the person in charge of the product, you may not be terribly concerned about how clean and well-structured the code is. The messier the code and the less modular the architecture is, the longer it takes and the more expensive it is to change your product. You intentionally slow down, so to speak, to go faster afterwards.
Product (and company) strategy is the backbone that guides productgoal-setting and roadmap definition, although it’s sometimes overlooked or confused with having a vision. Without it, product teams become feature teams focused on outputs and not outcomes. It is the guiding principle for OKRs and roadmaps.
We were so inspired by Tali’s enthusiasm that we just had to share her story here on the Product Talk blog. Do you have your own Product in Practice you’d like to share? Then, based on a defined productgoal, they were asked to prioritize a specific opportunity and explain their choice. You can submit your story here.
In the product planning model above, the vision describes the ultimate purpose for creating the product; the product strategy states how the vision will be realised; and the productroadmap states how the strategy will be implemented.
NAVIGATING THE NATURAL TENSION AMONG STAKEHOLDERS This is the first in a series on productroadmaps. The first post describes why roadmaps matter and who relies upon them. The roadmap is much more than a directive document that tells teams what to do by when. Battleground The productroadmap.
While I really appreciate this entrepreneurial aspect of our work, it can bring up tension, stress, and frustration when we are trying to progress our products towards agreed goals but are in danger of missing them, be it a sprint goal , productgoal on the roadmap , or a strategic user or business goal.
While I really appreciate this entrepreneurial aspect of our work, it can bring up tension, stress, and frustration when we are trying to progress our products towards agreed goals but are in danger of missing them, be it a sprint goal , productgoal on the roadmap , or a strategic user or business goal.
For example, I have seen product teams that create OKRs around meeting with customers, and engineering teams that created OKRs around closing the tech debt. The problem with this approach is that it leaves a huge gap in the company’s ability to deliver on its top OKRs: the product itself. Is that realistic?
Cindy who helps you manage the product started to come late to meetings. It can be tempting to ignore people issues and focus on product-related tasks like reviewing the product strategy , updating the productroadmap , and refining the product backlog. But this is hardly a recipe for success.
Anything in the top right, like ‘idea 7’, should go straight to the top of your roadmap. While ICE is definitely a cool tool to use, you might find that you need a more substantial method to meet your hunger for prioritisation. Scrap that roadmap, it’s time to pivot! This is where RICE can help. The RICE Method.
To understand the problem with technical debt roadmaps, we’ll start with a quote from renowned philosopher, Homer Simpson. When you create a dedicated roadmap for technical debt, you are removing the the problem from your immediate sight. In this article, we’ll discuss why technical debt roadmaps don’t work.
We organize all of the trending information in your field so you don't have to. Join 96,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content