Remove release-notes backlog
article thumbnail

3 Empowerment Levels in Product Management

Roman Pichler

2] The product backlog , or one of its subsets, and the release plan are the main artefacts you work with. You spend a significant amount of your time refining product backlog items, writing user stories , tracking the development progress, and talking to development team members.

article thumbnail

Five Product Owner Myths Busted

Roman Pichler

Myth #2: The product owner is a tactical role focused on managing the product backlog. The individual should carry out product discovery and strategy work in addition to taking care of the product backlog work. The SAFe product owner is tactical in nature and focuses on working on the product backlog and guiding the development teams.

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

What Should a Head of Product Do?

Roman Pichler

Note that I have kept the description of the responsibilities concise. For example, agree with the team members what goals should be used to manage the products, how product discovery is practised, how often the product strategy and roadmap are reviewed , how the right KPIs are selected , and how product backlog refinement is carried out.

article thumbnail

Beyond the Book: Navigating the Real-World Challenges of Managing a Product Roadmap

The Product Coalition

The best practice is to put them in the backlog, conduct discovery, identify the value, and then prioritize and place them on the roadmap. 1) Velocity — what is the rate of change of the product, and how often are changes released? The higher the velocity of release and the faster the rate of drift, the more often updates are required.

Roadmap 112
article thumbnail

So, You Have A Vision, Now What?

The Product Coalition

Once we had this basic flow, I added sticky notes in each step. The sticky note displayed the options and my preference. I created a release plan. Well, since we are working in quarterly releases?—?I I created a plan for two releases, and the rest was a backlog. The color coding was based on: Red ?—?open

Vision 158
article thumbnail

Report templates for less status meetings

Folding Burritos

Low-level information-passing is about keeping other updated about our work in progress and releases, so they’re able to do their jobs with more efficiency. When are our next releases happening? What have you released recently? What progress are you making on X? Anything we need to be concerned about? Goals / KPIs.

article thumbnail

A Learning Roadmap for Product People

Roman Pichler

Note that you may want to make the measures as specific as you can and state, for instance, the title of the books you intend to read. The fourth and final line states how you intend to meet the learning goals.

Roadmap 320