Skip to content
ProductManagement.com.br
ProductManagement.com.br

Um lugar aberto à discussão sobre produtos digitais

  • Product Management
    • Product Discovery – Dicas e Passos.
    • O Product Owner e o Business Analyst
    • Refinement Meeting: Por que e como fazer?
    • Visão geral do PO em projeto Ágil
    • Perfis legais para seguir no Twitter
  • Scrum
    • Scrum, o primeiro contato!
    • Ágil. Porque tantas tentativas falham?
    • O Product Owner e o Business Analyst
    • Ágil. Gestão do conhecimento, escopo, documentação, testes, falhas e mais…
    • Scrum. Gestão do conhecimento e mudanças de escopo
    • Ágil. Um pouco sobre documentação de regras, testes e comunicação
    • Refinement Meeting: Por que e como fazer?
    • Refinement Meeting: Respondendo as 6 dúvidas iniciais
    • Características de um bom Product Backlog – DEEP
    • Perfis legais para seguir no Twitter
  • English
    • Agile Product Ownership in a nutshell
    • Agile. Why so many projects fail?
    • Grooming the Product Backlog: Answering 6 initial questions
    • Great profiles to follow on Twitter
ProductManagement.com.br

Um lugar aberto à discussão sobre produtos digitais

Agile Product Ownership in a nutshell

Daniel Baldini, February 22, 2017February 24, 2017

Starting in Product Ownership?

I believe this is the best introductory presentation about Product Ownership.

If you would like to know the main topics of this video just click here.



Original Url: https://www.youtube.com/watch?v=502ILHjX9EE

Click here to download the complete drawing.

Main topics:

  • Agile from the Product Owner (PO) perspective.
  • PO has the real Product Vision and he has to share it.
  • Stakeholders are the product’s clients or users.
  • The Development Team is small, cross-functional and self-organizing.
  • The Development Team has a limited capacity in a “time-boxed” period.
  • PO is in charge of Product Backlog and needs to say no when a new feature proposed by a stakeholder doesn’t fit the Product Vision.
  •  PO need to “guess” the story size and value. He/She needs to communicate with Stakeholders and the Development Team in order to it.
  • Estimating and prioritization is a habit, not a process. Something important today can be obsolete tomorrow, and vice-versa.
  • Ideal Product Backlog has small stories at the front and big and imprecise ones at the back. Doing it in a “just in time” fashion give us better insights.
  • PO needs to recognize the “Types of Risks” that exist in which story.
  • PO needs to be able to prioritize short-term (reactive work) and long-term (pro-active) activities.
  • Building a product:
    • PO is responsible for building the right thing.
    • Development Team is responsible for building the thing right.
    • Coach (Scrum Master) wants to build the thing fast.
    • Keep trying to find the balance.
  • Be aware of Technical Debt.
  • Multiple teams working on the same product.
  • Success for PO usually is passion and communication.
  • If your organization doesn’t like truth and honesty, it probably won’t like Agile.

Back to the video.

[Portuguese Version]

English

Post navigation

Previous post
Next post

Related Posts

Grooming the Product Backlog: Answering 6 initial questions

February 25, 2017March 2, 2017

What is the concept? What is the aim? What are the activities? When should I have it? How long does it take? Who participates? I am sure those are the questions that come into our minds when we first think about Grooming sessions. Let’s go to the answers: Concept: To deepen/to detail the…

Read More

Agile. Why so many projects fail?

February 23, 2017February 28, 2017

The answer is quite easy and you should know, but I’ll show you a slide to explain it better. In a previous post, I have shown what I understand to be the greatest difference between a Traditional (Waterfall) Project and an Agile Project. When writing, the difference is tiny. But there…

Read More

Últimos posts

  • Product Discovery – Dicas e Passos.
  • Refinement Meeting: Por que e como fazer?
  • O Product Owner e o Business Analyst
  • Características de um bom Product Backlog – DEEP
  • Ágil. Gestão do conhecimento, escopo, documentação, testes, falhas e mais…

Comentários

  • Urânia Reis on Ágil. Porque tantas tentativas falham?
©2025 ProductManagement.com.br | WordPress Theme by SuperbThemes