Remove Product Strategy Remove Roadmap Remove Weak Development Team
article thumbnail

Dealing with an Underperforming Development Team

Roman Pichler

What is Bad Performance? Before I discuss how you can help an underachieving team, let’s briefly explore what good performance looks like, assuming that an agile, Scrum-based process is used. Second, the team participates in continuous discovery and strategizing , and its members regularly help refine the product backlog.

article thumbnail

10 Product Roadmapping Mistakes to Avoid

Roman Pichler

1 The Product Roadmap is a Feature-based Plan. Traditional product roadmaps 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.

Roadmap 337
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

A Learning Roadmap for Product People

Roman Pichler

Overview of the Learning Roadmap. Like a modern product roadmap, a learning roadmap states the specific outcomes or benefits you’d like to achieve to become a more competent product person, and it captures them in form of learning goals. To make these ideas more concrete, let’s look at a sample learning roadmap.

Roadmap 344
article thumbnail

Maximising Stakeholder Buy-in to Product Strategy and Product Roadmap

Roman Pichler

2] Figure 1: The Power-Interest Grid The grid divides stakeholders into four groups: crowd, subjects, context setters, and players depending on how interested they are in your product and how much power they have. Smaller strategy updates and product roadmapping decisions, however, are not as critical.

Roadmap 242
article thumbnail

Three Qualities of Great Product Roadmaps

Roman Pichler

Traditionally, product roadmaps 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. Second, it overlaps with the product backlog, especially when detailed features are used. Outcome-based).

Roadmap 290
article thumbnail

Building a Great Product Management Organization

Melissa Perri

I look at four dimensions for robust Product Organizations: Product Organizational Design Product Strategy Product Operations Product Culture Inside each of these are a few capabilities that are then broken down further into sub-capabilities that help me pinpoint where the issues are.

article thumbnail

Making Effective Product Decisions: Tips for Deciding with Stakeholders and Dev Teams

Roman Pichler

Be Clear on When to Involve the Stakeholders and Development Teams. Complex and high-impact decisions, however, are best made together with the stakeholders and development teams. Additionally, include the development team members in product backlog decisions , and always choose sprint goals together.