Food for Agile Thought’s issue #128—shared with 14,506 peers—covers disrupting companies—seven habits that make any organization highly vulnerable—, Jeff Sutherland’s new framework to scale scrum, and the movements that inspire the future of work.
We then dive into the advantages of autonomous product teams and learn that a bug-free product is not necessarily a sign of a quality mindset.
Lastly, if your stakeholders believe your team is a black box, why not build an information radiator? C. Kyle Jacobsen can help you with that.
Food for Agile Thought’s issue #127—shared with 14,292 peers—covers useless agile metric; we learn common excuses why continuous delivery would not work, and how to organize a big room planning.
We then talk about signs of toxic team culture, how design thinking, agile and lean fit together, and what to do when a team fails to deliver at the end of a sprint.
Lastly, we learn why experiments do not just happen to the best organizations but perhaps create them, and what product thinking has to do with it.
Food for Agile Thought’s issue #126—shared with 14,145 peers—covers the state of agile engineering in 2018, why creating and nurturing a groundswell of enthusiasm is essential for an agile transition, and what organizations need to focus on in search of (agile) excellence.
We then learn how any product-oriented organization can create a culture of experimentation and why the velocity of experimentation is probably not a vanity metric. Apropos metrics: there is a new list with anti-patterns available.
Lastly, McKinsey seems to get serious about ‘agile.’ Check out the trademarks McKinsey identified in all agile organizations and let me know your opinion in the comments.
Food for Agile Thought’s issue #125—shared with 14,043 peers—addresses the dark side of remote work, what scrum masters do not do, and why the whining about too many scrum meetings is baseless.
We then learn how to apply first principles to product management, and why knowing what not to build is essential today.
Lastly, we have a brief look at a new open source initiative: the agility assessment framework—its working title for the moment.
Food for Agile Thought’s issue #124—shared with 13,873 peers—addresses some symptoms of troubled agile transitions: low levels of engagement, difficulties in learning presumably simple patterns, optimizing for the own team while ignoring the organization.
We then learn what it takes to build trust, how to discover ‘your product’ without falling into the stage-gate process trap, and what product strategy concepts are currently en vogue.
Lastly, if you want to take your career as a scrum master or agile coach to the next level consider downloading my ‘How to Get Hired as a Scrum Master’ book—it is free on Amazon for five days.
Food for Agile Thought’s issue #123—shared with 13,624 peers—addresses Scrum 2018: Scrum Alliance’s latest survey is available, John Cutler’s opinion piece on today’s state of ‘Scrum,’ indications of lipstick agile to watch out for, and ten prevailing scrum myths.
We then focus on how to figure out what is worth building: from creating a bulletproof product strategy to developing an experimentation system and why you need to be careful when using the Net Promoter Score®¸
Lastly, we learn more about the organizational patterns of progressive companies. Have a successful 2018!
