There are three roles in a Scrum team: the ScrumMaster, the developer and the product owner. This last role might be the most important for a team that uses an Agile project management approach in software development. The product owner has the responsibility of building and prioritizing the backlog. If this is not done properly, you will just not build the right product. This article presents the certifications available for product owners in Scrum.
Scrum Product Owners do everything to drive the direction of the products and inspire the Agile team to work on a transcendental goal. They achieve this that by acting as an incredibly awesome team that works across functions, listening to customers and each other. Do you want to be a really awesome Product Owner team?
This presentation explores some uncomfortable realities about many present approaches and attitudes to product ownership in Agile and Scrum teams. Then, it journeys into the past to discover the top secret superpower that all teams working towards agility have, but often forget.
A Scrum team cannot deliver value without a good Product Owner. This is for me the most important role and it is not easy to keep an Agile balance between a long term business vision that could lead the team to success and the ability to adapt to change after receiving customer feedback. In this article, Zuzi Šochová shares a list of the most common mistakes made by Product Owners.
It all starts with doing the right thing. Agile has not changed the old computer wisdom of “garbage in, garbage out”. This is why Allan Kelly last book is dedicated to the art of Agile product ownership. As he wrote: “If a Scrum Master performs badly, the team simply fails to perform well. If the Product Owner performs badly, the whole product is in jeopardy”.
Is hiring for an Agile team (team member, scrummaster or product owner) different than hiring for a software development organization that follows another approach? Scrum.org and McKinsey & Company have recently published the results of a joint study exploring the values and traits that make agile teams successful. The goal of this document is to help and guide organizations with concepts and ways to better recruit and coach their teams.
Your product roadmap can basically set your life course as a designer/researcher so why is it so often that user feedback can get lost in the discussion over “Feasibility” of implementation. Without a clear roadmap, research and design can often not have the lead time needed for activities. This leads to a state of forever catching up and being reactionary.
Scrum Expert Copyright © 2009-2024 Martinig & Associates