Remove product-backlog-mistakes-to-avoid
article thumbnail

Seven Product Backlog Mistakes to Avoid

Roman Pichler

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.

article thumbnail

10 Product Strategy Mistakes to Avoid

Roman Pichler

Listen to the audio version of this article: [link] 1 No Strategy The first and most crucial mistake is to have no product strategy at all. When that’s the case, a product is usually progressed based on the features requested by the users and stakeholders. The strategy is therefore either too big or too narrow.

Vision 90
Insiders

Sign Up for our Newsletter

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

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. A feature-based product roadmap is easily mistaken for a commitment rather than a high-level plan that is likely to change.

Planning 125
article thumbnail

Exploring the Benefits of an Agile Application Modernization Approach

Leading Agile

As each capability is freed from the rat’s nest, working tested product is placed into the hands of the user or customer. As each capability is freed from the rat’s nest, working tested product is placed into the hands of the user or customer. Your products and user journeys leverage those capabilities to deliver value.

Agile 144
article thumbnail

Five Product Owner Myths Busted

Roman Pichler

Myth #1: The product owner must ensure that the stakeholders are satisfied. But the value a product creates is ultimately determined by its users: No product will be successful in the long run if it does not solve a specific user problem, create a tangible benefit, or help the users achieve a specific goal.

article thumbnail

Best Tips for Effective Facilitation of Sprint Planning

Agilemania

As a result, we waste time on unnecessary tasks that won’t give us the expected result during product delivery. Sprint planning happens at the beginning of the sprint, where the entire scrum team defines the sprint goal and determines the sprint backlog. This leads them to a lot of hassle during sprint planning.

article thumbnail

5 Things You Should Never Say (or Do) During Sprint Planning

Cprime

Many years ago, a friend of mine once told me: “Sometimes the best way to find what works for your team is to avoid making basic mistakes”. Let’s take a look at possibly the most important Scrum event, Sprint Planning, and explore a few common mistakes. to apply this framework.