Remove Agile Remove Roadmap Remove Weak Development Team Remove Workshop
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. This makes the product roadmap more susceptible to change and it increases the effort to update it.

Roadmap 268
article thumbnail

10 Tips for Creating an Agile Product Roadmap

Roman Pichler

Whenever you are faced with an agile, dynamic environment—be it that your product is young and is experiencing significant change or that the market is dynamic with new competitors or technologies introducing change, you should work with a goal-oriented product roadmap, sometimes also referred to as theme-based. 4 Keep it Simple.

Roadmap 328
Insiders

Sign Up for our Newsletter

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

Trending Sources

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. This makes the product roadmap more susceptible to change and it increases the effort to update it.

Roadmap 156
article thumbnail

How Agile Has Changed Product Management

Roman Pichler

Before the advent of agile frameworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together product roadmap, write a requirements specification, and then hand it off to a project manager.

Agile 248
article thumbnail

Seven Product Backlog Mistakes to Avoid

Roman Pichler

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. The Product Backlog is Too Big.

article thumbnail

3 Empowerment Levels in Product Management

Roman Pichler

1] Figure 1: An Empowerment Model for Product People and Teams Level one represents the authority to decide how features are detailed and guide their implementation. Level three, finally, allows product people and teams to develop the product strategy including the value proposition and business goals.

article thumbnail

How Agile Has Changed Product Management

Roman Pichler

Before the advent of agile frameworks like Scrum , a product person—the product manager—would typically carry out the market research, compile a market requirements specification, create a business case, put together product roadmap, write a requirements specification, and then hand it off to a project manager.

Agile 156