Scrum has proven to be an effective product delivery framework for digital products like applications or apps. However, Scrum is equally 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 team by gating and prioritizing the product backlog. How that is supposed to happen is nowhere described in the Scrum Guide. Consequently, when everyone is for himself, 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.
Food for Agile Thought’s issue #114—shared with 12,308 peers—focuses on team building and rockstar engineers, or better: the lack of them. We also come back to psychological safety and wonder whether the term is overused or abused?
Steve Denning explains why SAFe == pre-Copernican command and control thinking, and we learn what misconception lets software product spiral out of control.
Lastly, Kate Bennet shares the results of her survey on product prioritization methods.
Food for Agile Thought’s issue #113—shared with 12,181 peers—covers scaling Spotify, why technical debt gets out of control, how to go faster, and that customer centricity requires changes to the organization.
We also have a look at ‘Cost of Delay’ as a concept and learn that buildings MVPs might be counterproductive, and to make (product) decisions without a doubt.
Lastly, Hiten Shah considers Trello a failure—find out why.