Remove Document Remove Product Goals Remove Vision
article thumbnail

Building High-Performing Product Teams

Roman Pichler

Figure 2: Roman’s Goal-Setting Framework with Product Management Artefacts The goal-setting framework shown in Figure 2 suggests that a product team needs four different objectives: a product vision, user and business goals, product goals, and sprint goals.

article thumbnail

Product Teams in Scrum

Roman Pichler

This team consists of a product owner , a Scrum Master , and several developers, which are also known as development team. Forming such a team connects the person in charge of the product—the product owner—with the people who design, architect, program, test, and document the solution—the developers.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Five Product Owner Myths Busted

Roman Pichler

This requires full-stack ownership : having the authority to make strategic product decisions in addition to tactical ones. Consequently, a Scrum product owner should own a product in its entirety—from the product vision to the product details.

article thumbnail

How to Use Product Goals and Initiatives to Drive and Measure Success

Userpilot

Setting smart product goals 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 product goal, the difference between goals and product initiatives, how to set them and make them work with your product backlog, and more.

article thumbnail

Integrate Product Owners into Many Teams to Create Good Product Goals, Part 3

Johanna Rothman

Some product owners think they're supposed to fill out a complete backlog, including all the UI designs for the product before the team can start. That's a more traditional product requirements document, and I've never seen that work.) And only you know which collaborations matter more right now.

article thumbnail

Technical Debt and Product Success

Roman Pichler

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.

article thumbnail

A Practical Guide for Product Strategy From Almundo: A Case Study:

Mind the Product

Product (and company) strategy is the backbone that guides product goal-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. The same document holds the OKRs for every product team.