TL; DR: Scrum’s Failure — Food for Agile Thought #389
Welcome to the 389th edition of the Food for Agile Thought newsletter, shared with 46,163 peers. This week, we delve into Scrum’s failure: Jason Godesky reminds us that few have ever worked in a true Scrum team, but many have in a Scrum cargo cult environment. Moreover, we delve into “bias and noise” and how they influence forecasting, and we learn how you can use Fluid Scrum Teams to manage multiple data products over various Sprints. Also, in shameless self-promotion, I want to point to the No Nonsense Agile Podcast that Murray Robinson, Shane Gibson, and I recorded recently. (Speaking of anti-patterns: There is also a new article on Jira and its perils if misused, see below.)
Then, we analyze the fundamental misalignment between the ‘business’ — focusing on one customer at a time — and ‘product/engineering,’ focusing on the overall impact for the installed base. Additionally, we point to the importance of embracing a learning mindset as the driver of innovation while process, vetos, institutional memory, and the vilification of failure work against it, and we share a practical and actionable list of recommendations to create a ProductOps handbook.
Finally, we suggest five experiments to help foster a safe working environment, from equal speaking time during meetings to celebrating failure, plus a new tool to ease the often challenging task of communicating project issues: the Definition of Broken. More tools are from John Cutler, who points to the free template library of the complete North Star metrics framework. Lastly, Nicole Abi-Esber and Juliana Schroeder claim that people underestimate how much others want to receive feedback.