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.
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.
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).
Be Clear on When to Involve the Stakeholders and DevelopmentTeams. Complex and high-impact decisions, however, are best made together with the stakeholders and developmentteams. Additionally, include the developmentteam members in product backlog decisions , and always choose sprint goals together.
The Product Backlog is Too Big. A few years ago, I was asked to help a healthcare company with their agile transition and its impact on product management. One of the challenges the agile transition team was concerned about was the choice of the right product backlog tool, which at first seemed odd to me.
Instead, you should engage the stakeholders, leverage their expertise, and generate as much buy-in as possible , as I explain in more detail in my article “ Stakeholder Management Tips for Product People.” ” But do not allow people to dominate and tell you what to do, and don’t agree to a weak compromise.
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. Listen to this article: [link].
Listen to the audio version of this article: [link] 1 Complement Scrum with a Product Discovery and Strategy Process Scrum is a simple framework that helps teamsdevelop successful products. Continue the discovery and strategy work while the product is being developed. But don’t stop there.
While common sense suggests that managing a product without the right measurements is not a sensible approach, I’ve seen productteams who did not use any KPIs. Consequently, these teams relied on: Anecdotal feedback : “Customers love our product, they told me so.” 3 Stakeholder or Big Boss Dictates KPIs.
The first one carries the risk of being a feature broker and offering a product that has a weak value proposition, gives rise to a poor user experience, and consists of a loose collection of features. A stakeholder is anyone who has a stake in your product, who is affected by it, or who shows an interest in the offering.
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).
For product strategy and roadmap meetings, I recommend involving the key stakeholders , for example, someone from sales, marketing, support, and finance, as well as developmentteam representatives—ideally members who know about the user experience (UX), architecture, and technologies. Close the meeting.
Staffing : Help find people who have the right skills and are motivated to work on the product and who can fill the roles. For example, I’ve seen organisations where the Scrum Masters work with HR and the developmentteams to recruit new team members. The individual is not a product backlog manager or a user story writer.
Consequently, your focus shifts from managing a product to looking after the product people on your team and empowering them to do a great job. For instance, you might show the individuals how they can make effective strategic product decisions, create an actionable productroadmap, and effectively use the right KPIs.
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. Furthermore, consider the life cycle stage of your product.
Be Clear on When to Involve the Stakeholders and DevelopmentTeams. Complex and high-impact decisions, however, are best made together with the stakeholders and developmentteams. Additionally, include the developmentteam members in product backlog decisions , and always choose sprint goals together.
Here is why: We routinely interact with individuals who have different perspectives, interest, and needs, such as users, customers, stakeholders , developmentteam members. Users don’t always have the same wants and needs as customers, and the ideas of the stakeholders and dev team may diverge.
Here is why: We routinely interact with individuals who have different perspectives, interest, and needs, such as users, customers, stakeholders , developmentteam members. Users don’t always have the same wants and needs as customers, and the ideas of the stakeholders and dev team may diverge.
Instead, you should engage the stakeholders, leverage their expertise, and generate as much buy-in as possible , as I explain in more detail in my article “ Stakeholder Management Tips for Product People.” ” But do not allow people to dominate and tell you what to do, and don’t agree to a weak compromise.
Here are four examples: Joe, the sales rep, has promised a feature to an important customer without first talking to you—the person in charge of the product. Sue, the Scrum Master , wanted to help the developmentteam get better at sprint planning. But the team still over-commits and under-delivers.
Each week I scour articles, wading through the dogs, and bringing you the best insights to help product managers, developers, and innovators be heroes. Another reminder why new products need a workable business model. Products (wrongly) get created this way – product first, customer second, revenue third.
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.
TL;DR Feature ideation is a process through which productteams brainstorm ideas for new features to introduce to their product. It helps you meet user needs, enhance user experience , improve product value, and gain a competitive advantage. Why do you need feature ideation in your productdevelopment process?
Typically this would be a cross functional team of C- level and director-level people. It’s led by the product manager responsible for the product line, and it happens once every half year or less. All product managers in the company should produce a state of product deck and present it. ProductRoadmap.
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.
Consequently, your focus shifts from managing a product to looking after the product people on your team and empowering them to do a great job. For instance, you might show the individuals how they can make effective strategic product decisions, create an actionable productroadmap, and effectively use the right KPIs.
We explain how to create a successful product strategy, the role of product strategy in prioritization, and how to align your prioritization efforts with your strategy. However, to learn more, you’ll have to listen to the man himself as he develops the topic at the 2024 Product Drive Summit.
These thoughtful considerations will ensure that you have the correct assessment of your company’s UX maturity , your product’s current standing, future needs, and your user requirements — all of which will form the foundation of your UX budget. Have you defined your short-term and long-term productgoals?
Developing and releasing sophisticated products with all the bells and whistles imaginable might seem like a great idea. Overengineered products are difficult to use, filled with bugs, and instead of improving your users’ lives, they make them unnecessarily complicated. Why do developers overengineer software products?
Market research and customer discovery help validate ideas and make sure the market is ready for the product. Product failure is often attributed to poor UI/UX. Make your UI easy to navigate so that customers can easily learn how to use it and can experience product value quickly. Let’s look at these in more detail.
Function friction is primarily about users being blocked from reaching their productgoals because of an error, poor UX, or other factors. Opportunity friction is driven by the gap between what a user expects to be able to do, and the functionality of your product as it stands. Not all friction is bad.
Product differentiation and positioning are important aspects of strategic product management because they allow you to build a product that meets the needs of the right customers in the right market and stand out from the crowd. Goals are important aspects of the product strategy. Source: Pragmatic Institute.
Working as a product manager can be a busy, unpredictable and octopus-like existence. Bringing team members together, organizing user research, product demos, road mapping and more. If you’re a mobile app product manager there’s a whole additional layer of complexity to add to that cake.
Part 3 brings together the Product specific Vision, Roadmap and Goals. Product Vision puts a company’s Vision and Mission into action The Product Vision ensures the Roadmap reflects the priorities which matter the most to the company’s customers and to the company. What ground has been covered?
Productdevelopment is exhilarating. There is something special about a team rallying around a vision and creating a product that users love. . However, it isn’t fun to redo a product every three years. Unfortunately, technical debt can do that to your team. Align Technology & ProductRoadmaps.
Paul Ortchanian recognized this inconsistency, and it sparked the creation of what is now known as Bain Public: a company dedicated to helping local companies make smart product decisions through an organizing principle for allocation of resources: the roadmap. Building Roadmaps. Transitionary Leadership.
I’ve worked in companies that have both roles, companies that only have project managers and companies that only have product managers. Several prominent blogs that I’ve read assert that project managers and product managers are ‘two sides of the same coin’ and should work harmoniously to deliver productgoals.
On the show, Paul will be talking about discipline in product and good habits that are needed with completing roadmaps. Reaching a productgoal and accelerating a company’s success is not possible unless everyone from all teams, including engineers, marketers, sales, support, etc. About the Episode.
What is a product analytics framework and why is it important? We also look at: Different types of analyses to include in your framework How to develop a product analytics framework And, the best product analytics tools. Solid product analytics tools include Amplitude , Google Analytics 4 (GA4) , and Hotjar.
Great teams assemble individuals with differing skill sets, perspectives, and experiences. For example, Iron Man and Captain America leading the Avengers or Superman, Batman, and Wonder Woman teaming up as the Justice League. Many productteams now have their own team of super-powered individuals banding together for a common cause.
Technical program manager (TPM) roles range from mid to senior-level positions that support organizations with their productgoals. They work with leaders and their own teams across organizations. TPMs must communicate strategies, roadmaps, and program issues with all key stakeholders.
As a product manager, you may have already learned how to plan and prioritize a productroadmap. In response to a Reddit question asking whether there are product roles that exist with a work-life balance, one user answered: "It depends. Make a note of what type of product management you are doing. ScienceDirect.
by Ashley Sefferman , Head of Content at Apptentive When Ben Horowitz published his thoughts on the idea that product managers are the CEO of their products in “ Good Product Manager/BadProduct Manager ” nearly two decades ago, the concept was profound, but divisive. What are the goals of individual teams?
Perhaps product people will write a better user story, or prioritize a backlog, or produce different roadmap; these are tactical activities. With this context, I’ve decided to take some of the content I included in The Product Manager’s Survival Guide, 2nd ed., Sometimes an organization has one product, sometimes it has several.
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