Scrum does not define a "product", and how you define your "product" has huge implications for the organization. Broader definitions of product (a) focus on solving actual customer problems (b) avoids local optimizations in the organization (c) eliminates management of dependencies between different micro- "products" (d) and hence enables organization to "be more agile"
"Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team." - The Scrum Guide. When the whole Scrum Team is self-organizing (in addition to the Dev. Team being self-organizing in executing the Sprint Backlog), understanding the context of Product Owner -… Continue reading [Product Owner – Dev. Team] Ladder of Empowerment
Scrum, today, has become the most popular framework. Naturally, the folklore around it also has grown over the course of time. Scrum was first published in 1995, and Scrum Alliance officially founded in 2001. During those times, the main source of Scrum was the creators of the framework. Naturally, word of mouth has its limitations… Continue reading Scrum: folktales, facts, alternate- facts, and other nonsense !!
One PO per Development Team instead of one PO per Product Multiple PO for multiple smaller related "products" (e.g. PO for Android PowerPoint, PO for iPhone PowerPoint, PO for Windows Desktop PowerPoint, PO for Mac PowerPoint, PO for PowerPoint 365) There is only ONE product here - PowerPoint. Android, iPhone, Windows Desktop, etc are different… Continue reading Dysfunctional Product Owner Patterns