Skip to content
Hallway
0:00 / 0:00

#agile#scrum#productowner

Agile Product Ownership in a Nutshell

Henrik Kniberg

161K subscribers • 1 video on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • Presented by Henrik Kniberg

Beginner. No background in the topic needed.

4.8M views14 years ago2 recommendations

Tools and practiceCareers and interviewsCode review and teamworkDeveloper productivityEngineering management

Henrik Kniberg explains the role of the Product Owner, backlog management, and agile delivery dynamics in an animated overview.

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 see this is a high level summary. For translated versions & translation guide, see blog.crisp.se/2012/10/25/henrikkniberg/agile-product-ownersh… Do you want to contribute subtitles to this video? Here is the community translation link: youtube.com/timedtext_video?v=502ILHjX9EE&ref=share Special thanks to Alistair Cockburn, Tom & Mary Poppendieck, Jeff Patton, Ron Jeffries, Jeff Sutherland, and Michael Dubakov for providing many of the models, metaphors, and ideas that I use in this presentation. Download the complete drawing here: dropbox.com/s/ph3spbc3evgoh3m/PO-in-a-nutshell.png Downloadable version of the video here: dropbox.com/s/h3fzydsss7sgqjd/PO-in-a-nutshell.mov PS: The intro & outtro song is just me jamming in my home studio. I bought a cool half-acoustic guitar a few months ago and was looking for an excuse to make use of it :o) Tools used: Artrage (drawing program), Wacom Intuos 5 (drawing tablet), Screenflow (screen & audio capture).

Why it's here

2 people recommend this

What people say. Highly recommended as the clearest and most concise explanation of Agile product ownership and backlog management.

Moments people linked to

u/LogicRaven_in r/ExperiencedDevs • Recommends

On “How important is learning about Agile if I want to move to a startup”

…our peace of mind, do a short course on Scrum and/or Kanban. Epic is similar to a project - a bigger piece of delivery that has multiple subelements, benefit hypothesis and sometimes acceptance criteria. Product owner is often responsible for the "what and why" for the team, while engineers are responsible for the "how". Here is a good summary: link to this video Agile well done is a game changer and a lot of fun. Engineers get ownership and are co-creators of new features. Teams are often cross-functional, goals are on product and team level (not individual). Agile done on the corporate way with cargo culting - taking the artifacts and process elements of agile without mindset change - can be dem…
5View on Reddit

u/NoLengthiness9942in r/programming • Recommends

On “Someone starts negotiating your team's estimates, saying, 'No, it's less effort than that!' Why is that a bad sign? How to move the discussion in the right direction?”

u/Green0Photon, it sounds like there are a lot of things out of place. Many of the problems you describe are the results of running the development teams at an unsustainable pace. Check out this video by Henrik Kniberg that explains this problem very well:[video If the management team wants higher output, the **first rule is not overloading the team with more work** because this has the opposite effect. Run your sprints at a sustainable pace. In other words, only start as many stories as you can complete during the sprint. Note that a certain percentage of the backlog should always include process improvements. Dev team decides what to improve on and not management. Secondly, I would run…
3View on Reddit

u/NoLengthiness9942in r/programming • Recommends

On “Someone starts negotiating your team's estimates, saying, 'No, it's less effort than that!' Why is that a bad sign? How to move the discussion in the right direction?”

You are right; the problem is challenging. Because the root cause lies in that companies are set up to deliver results on quarterly earning calls. Often the management team is incentivized to deliver key results every three months. In this environment, you have to be an exceptional leader to keep your job and follow, often counterintuitive ideas such as those I mentioned above. Because many of these solutions return results in the long term, they will likely upset internal stakeholders and deliver poorly on key results in the short term. Therefore few managers are brave enough take this road. However, there are exceptions. Marty Cagan talks about this in [this video, where he talks about t…
2View on Reddit

u/NoLengthiness9942in r/programming • Recommends

On “Are you using story points and struggling with explaining to someone how you convert story points to a time of delivery? Here is how.”

…imate of the overall effort that will be required to fully implement a product backlog item or any other piece of work. Estimates are then used to answer questions such as 1. When is feature A expected to be delivered? 2. What will be complete by end of next quarter? Also check out Henrik Kniberg youtube video covering these questions here: * [video **Second** >Story points are complexity. Complexity is a factor that 'goes into story points' as Mike Cohn explains in his article. However complexity is not the definition of story points, it is only one of many factors that impacts the effort to complete a story. Quoting Mike Cohn's same article again : >Because story points represe…
-1View on Reddit