Food for Agile Thought’s issue #146—shared with 17,791 peers—addresses finding agile metrics, how to play the product game safe and lose, and why BDD is an integral part of business agility.
We also ask yourselves: Should an agile coach rather be an organizational psychotherapist? Or what are you doing all day if you’re supporting a single team as a scrum master?
Lastly, our gut feeling is confirmed that innovation does not happen under pressure as well as that ‘saying yes’ is not scaling technique to build successful products. (Fortunately, there are also six ways how to accomplish growth without trying to be everybody’s darling.)
Food for Agile Thought’s issue #145—shared with 17,732 peers—addresses how to make agile work for you, how graphics can massively improve your facilitation skills, and how you can identify friends and foes with an organizational design analysis.
We also get a better understanding of Kanban Cadences, how to sell and prioritize non-feature work such as refactoring, and why merely shipping code does not mean you understand the philosophy of Kaizen.
Lastly, learn new tips and trick on how to deal with HIPPOs and their pet projects in your organization.
Food for Agile Thought’s issue #144—shared with 17,591 peers—covers Mary Meeker’s epic report on Internet trends 2018, the background on why and how Amazon figured out the benefits of Amazon Prime, and why smart organizations leave the decision making to those closest to a problem.
We also appreciate Setapp’s detailed process to run product-/market fit analyses, and we learn why improving flow is the Swiss Army knife to solving all kind of issues.
Lastly, Leon Tranter makes a compelling pitch to dare more Kanban, and yes, running experiments will reduce output — if you ignore flow basics in the process.
Food for Agile Thought’s issue #143—shared with 17,473 peers—covers the pain of scrum teams working for ignorant management and improves our problem-solving capacity thanks to mental models from the circle of competence to Hanlon’s razor.
We applaud Mike Cohn for sharing ten practices, a scrum master should take to heart, and we learn how to create an agile community of practice and why that is a critical success factor. Also, we embrace the idea of guerilla user testing and building an information radiator for your team.
Lastly, we enjoy Des Traynor’s talk about figuring out what is worth building and taking it from there with style.
Food for Agile Thought’s issue #142—shared with 17,322 peers—covers corporate innovation failure patterns, dives into flow metrics for Scrum, and asks: does more planning make the team more successful?
We also shed light on systemic issues that may trigger bad behavior in people and try to understand better whether design thinking is indeed “BS.” (Some do not think so, a Danish toy manufacturer, for example, check their case study on running design thinking at scale.)
Lastly, we like to invite you to participate in the Scrum Master Trends Survey 2018 — a joined-venture of Scrum.org and Age of Product.
Food for Agile Thought’s issue #141—shared with 17,129 peers—analyzes why ‘agile’ is the most important social technology since Taylorism. Although, the proxy discussion of ‘outcome vs. output’ raging in many organizations signals that organizational debt is still a wide-spread issue.
We also cover the latest opportunities that innovative technology provides—unless your organization suffers from the not-invented-here syndrome, of course. (We also feature a list of 50 epic corporate innovation failures.)
Lastly, we get into the trenches and ask: why should teams not select themselves?
