Learn how individual incentives and outdated organizational structures — fostering personal agendas and local optimization efforts — manifest themselves in Scrum stakeholder anti-patterns that easily impede any agile transformation to a product-led organization.
During this workshop, Valerio Zanini and Zeina Zeitouni explored the Zones of Value Framework that Agile and Product teams can use to build better products. We recorded this video at the 31st Hands-on Agile meetup of April 20, 2021.
📺 Watch the video with Valerio Zanini & Zeina Zeitouni now: Hands-on Agile #31: The Zones of Value Framework .
Yes, even absolute beginners can prototype an app. And learn a lot about agile product management, Scrum, empiricism, product design, and user experience along the way.
If you intend to live up to Scrum and agile product development’s full potential, creating a shared understanding of how empiricism works among all co-workers in your organization is essential. This low-cost exercise of creating clickable prototypes will significantly improve your organization’s agile transformation.
Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. What product discovery part, you may think now. And this is precisely the point: The Product Owner miraculously identifies what is the best way to proceed as a Scrum Team by managing the Product Backlog. How that is supposed to happen is nowhere described in the Scrum Guide. Consequently, when everyone is for themselves, product discovery anti-patterns emerge.
From sunk costs, HIPPO-ism, my-budget-my-features to self-fulfilling prophecies — learn more about the numerous product discovery anti-patterns that can manifest themselves when you try to fill Scrum’s product discovery void.
The following 70 Scrum Master theses describe the role of a holistic product creation perspective.
The theses cover the accountabilities of the Scrum Master from product discovery to product delivery in a hands-on practical manner. On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. On the other hand, the Scrum Master theses also cover, for example, the relationship with the Product Owner, they deal with agile metrics, and how to kick-off an agile transition, thus moving beyond the original framework of the Scrum Guide.
There is one product, one Product Owner, one Product Backlog — a simple rule. How is that supposed to scale, you might ask, isn’t that approach turning the Product Owner into the Scrum team’s bottleneck, impeding value creation rather than spearheading it? Well, cargo cult Scrum might end up in that dead-end. The trick to avoiding this fate is to start including the Development Team as early as possible in Product Backlog management which requires a product mindset.
Learn more about how to kick-off this process with an initial day-long product mindset workshop for your Scrum team.
