The product owner role is responsible that the production of the Scrum team meets the requirements of the customers and deliver value for the organization. This is an important role that requires specific skills. But how do you know that your are doing well? The Growing Agile team as created a self-assessment for product owners.
The LAST conference is a one-day conference about Lean, Agile, Systems Thinking that takes place in Melbourne, Australia. It is a event for practitioners that encourages participation and interaction via talks, workshops and activities.
Shoddy software quality, disgruntled customers, missed deadlines… Such is daily life in many software companies. But there exists a better way. This presentation tells a story of turning around a demoralized and disengaged group of developers into a high performing team, while improving software quality, customer satisfaction and reducing technical debt.
In an ideal Agile world, the Scrum team is always completing all the selected user stories at the end of the sprint. In the real world however, there might be some product backlog items that don’t have a “done” status, but are only partially finished. Should you split them for the next sprint? In this article, Daniel Zacharias gives you four reasons why it is a bad idea to split unfinished product backlog items.
As with everything else related to agile, the nature of the Product Owner role, and whether it is needed or all, depends a great deal on context. As teams discover this, it leads to some common questions: What do Product Owners really do? Do we even need Product Owners?
The Agnostic Agile Oath is a movement that aims at recognizing the importance of being agnostic with agility at any level. As it is stated on the web site: “one size does not fit all, one framework is not the answer, and the what’s and the how’s of what needs to be done, should be suited to customer context and to a wider strategic vision.”
This is a talk about how shifting the focus from craft to product has affected my company. Our delivery teams are required everyday to make trade offs between what would the best technical solution and the one that is right for the product they are delivering. Ultimately, we get paid to solve business problems, not to be perfectionists.
Scrum Expert Copyright © 2009-2024 Martinig & Associates