Photo by Eprism Studio on Pexels.com

What knowledge did I experiment with last week?

What is the expected outcome?

How did I do?

What are the actual results?

What works, what doesn’t?

How do I feel after doing this implementation?

What do I expect to do next?

Keywords

  • Product vision
  • 4-step Product Strategy
  • User Story & mapping
  • Incremental
  • MVP and Product Roadmap
  • Product backlog
  • Definition of Done (DoD)
  • Backlog Grooming and 10 Techniques
  • Estimation and Planning Poker
  • Release plan and Phasing
  • Velocity and Risk Management
  • Burndown Chart and Effort

Notes

  • The product vision is a brief statement of the desired future state that would be achieved by developing and deploying a product. A properly envisioned project provides a definitive path that can best fulfill the project’s objectives or goals.
  • An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable.
  • The Definition of Done is an agreed-upon set of items that must be completed before a project or user story can be considered complete.
  • Product backlog grooming, also called product backlog refinement or backlog management, is an ongoing process in Agile development, in which the product owner and relevant stakeholders make sure that: The product backlog has the right items. The backlog items are prioritized.
  • Velocity is an indication of the average amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Development Team for use within the Scrum Team. There is no such thing as a Good Velocity or a Bad Velocity.
  • A burn-down chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining. Burn-down charts are used to predict your team’s likelihood of completing their work in the time available
  • In Scrum Projects, Estimation is done by the entire team during Sprint Planning Meeting. The objective of the Estimation would be to consider the User Stories for the Sprint by Priority and by the Ability of the team to deliver during the Time Box of the Sprint.

Relevant Questions

  • What could be done as a Product Owner with an Agile Coach mindset?
  • How can I ensure to avoid abusing the release train as a Product Owner, acting Scrum Master?
  • Is there another way of using the Poker Planning for the new team?
  • Does my team understand the Traditional and DSDM model?
  • Lean startup and how to work with team?

Product Owner for Mobile Games