Food for Agile Thought’s issue #214—shared with 23,916 peers—delves into Scrum agility; we follow a notion for time-based estimates, and we learn more about similarities and differences between Cynefin and the Stacey matrix.
We also consider the suggestion to skip standups as those are supposedly the worst breed of time-wasting status update meetings; we appreciate an infographic on output, outcome, and impact, and follow AirBnB to Cuba.
Lastly, we applaud an engineer for sharing his take on the role of the Product Owner.
Food for Agile Thought’s issue #213—shared with 23,845 peers—delves into how Liberating Structures rescue Scrum; we borrow Swedish ideas on agile leadership beyond the so-called ‘Spotify model,’ and we learn to create an environment that is attractive to introverts.
We also consider pair coaching; we learn how to include stakeholders in product decisions while managing their expectations, and we dare to look at some math, namely Cost of Delay.
Lastly, we shed light on Mr. Amazon’s grand plan for the universe.
Food for Agile Thought’s issue #212—shared with 23,794 peers—delves into coach assessment options; we learn how to help teams out of being stuck in discussions, and we gain more insight into the challenges of moving from directive to supportive leadership.
We also embrace the qualities that impact mapping brings to product discovery; we appreciate a new approach to making product decisions, and we will stop ignoring our competition.
Lastly, we are grateful that someone asked the obvious question: Is ‘Agile’ keeping us too focused on ‘building stuff?’
Food for Agile Thought’s issue #211—shared with 23,728 peers—celebrates John Cutler’s Feature Factory Reloaded; we bust the myth that not having a Sprint Goal would be okay, and we learn how to maximize collaboration time with distributes teams.
We also ask: Is it time to eliminate Scrum’s specialized role of the Product Owner? We then delve into how to gain a competitive edge, and we consider basing our product thinking on a set of fundamental propositions.
Lastly, we enjoy Shane Parrish’s excursion into the mental model behind root cause analysis.
Food for Agile Thought’s issue #210—shared with 23,637 peers—analyzes why customer journey teams may be superior to cross-functional teams; we enjoy a list of anti -agile personality types, and we listen to Mr. DevOps on how to build high-performance organizations.
We also help product managers to understand user research better; we delve into the most annoying collaboration mistakes of product teams, and we grasp the prerequisites of product-market fit.
Lastly, we thank Andy Cleff for compiling a list of approaches to measure team health and morale.
Food for Agile Thought’s issue #209—shared with 23,558 peers—delves into Design Thinking habits; we consider how to turn dark ‘agile’ into a value-driven approach again, and we go back once again to antipatterns of organizational agility.
We also address validating hypotheses beyond an ordinary A/B-test; we learn how to orchestrate continuous experimentation for fun and profit, and we applaud Jeff Gothelf for sharing the second version of the Lean UX canvas with the community.
Lastly, we put ‘bugs’ into an agile context, starting with a moth in 1946.
