Product Owner resources

Adapted from Crisp's blog by Henrik Kniberg. Explaining his MVP drawing. This drawing shows up all over the place, in articles and presentations, even in a b...

One of the main responsibilities of the Product Owner is managing the product backlog. It’s a team effort to refine the backlog, but the Product Owner is the one responsible for prioritising the backlog. This is a challenging job. Product Owners who are new in their role think the backlog only contains user stories for new features. But they soon find out this is only a part of the backlog. But what are the other parts? And how to find the right balance between them? This is where the ‘backlog prioritisation quadrant’ shows its value.

What is a user story? Learn about agile user stories and examples so you can stop writing about requirements and start talking about them.

Technical debt (also known as design debt[1] or code debt) is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer.[2]

Understand the desirable qualities of successful product owners.

Find out how the product roadmap and the product backlog relate, and who should own the two artefacts.

Have you ever worked on a Scrum project where the overall goal was not clear? Where you had a product backlog but the people involved in the development effort only vaguely understood the purpose of the release? It happens more frequently than any of us would like, even on projects with multi-million dollar budgets! Often Scrum’s emphasis on “getting work done” is misunderstood as a rush to develop with not enough thought to where the project should be going. Don’t make that mistake. Every Scrum project needs a product vision that acts as the project’s true north, sets the direction and guides the Scrum team. It is the overarching goal everyone must share – Product Owner, ScrumMaster, team, management, customers and other stakeholders. As Ken Schwaber puts it: “The minimum plan necessary to start a Scrum project consists of a vision and a Product Backlog. The vision describes why the project is being undertaken and what the desired end state is.” (Schwaber 2004, p. 68)

Scrum is a framework for developing and sustaining complex products. This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together. Ken Schwaber and Jeff Sutherland developed Scrum; the Scrum Guide is written and provided by them. Together, they stand behind the Scrum Guide.

This presentation was recorded at GOTO Copenhagen 2015 http://gotocph.com Gabrielle Benefield - Agile/Lean product and UX coach Renee Tsielepi - Head of IT -...

Today, most products and services organizations focus their collective attention overwhelmingly on delivering things right – on schedule, on budget, with complete scope and quality. Relatively little collective attention is paid to whether they are delivering the right things that solve their real problems. Gabrielle will talk about moving to an outcome delivery model using Mobius; including case studies and how to get started. Mobius is the double-loop learning infinite loop, helping you to focus on what problem to address, how to detect if it’s the right problem to address, how to get and analyze feedback to decide whether to continue or change tracks. This training also give you the official CSPO certification from Scrum Alliance.

Agile Product Management with Scrum: Creating Products that Customers Love (Addison-Wesley Signature Series (Cohn)) [Roman Pichler] on Amazon.com. *FREE* shipping on qualifying offers. The First Guide to Scrum-Based Agile Product Management   In Agile Product Management with Scrum

This is basically a 1 day product ownership course compressed into 15 minute animated presentation. There's obviously more to product ownership than this, so...