Food for Agile Thought’s issue #134—shared with 15,621 peers—focuses on agile failure patterns in organizations, at the leadership and the operational level.
We also learn new tricks how to deal with unexpected work during a sprint, which might come handy when agile coaching by virtual reality techniques finally overcomes the Manifesto’s face-to-face mantra. Supposedly, that will happen in a few years time.
Lastly, we revisit the fate of Yahoo where having the best and brightest at the right place at the right time did not prevent Yahoo’s decline and—ultimately—demise.
Food for Agile Thought’s issue #133—shared with 15,436 peers—explains why agile Taylorism — or introducing ‘agile’ by a command and control — is a futile approach. We also learn that competing and collaborating do not have to be mutually exclusive while becoming a learning organization.
We get a better understanding how continuous product discovery works in practice, how to avoid triggering your customers’ resistance to (product) changes, and why Geoffrey Moore might have been wrong.
Lastly, we enjoy the opportunity to learn more about becoming agile in distributed teams—with a free ebook courtesy of InfoQ.
Food for Agile Thought’s issue #132—shared with 15,184 peers—covers the latest version of the Agile Fluency ™ Model. Moreover, we learn why we are particularly bad at planning projects of all kind, and how visualizing with LEGO® may add to your organization’s bottom line.
We also find out how to deal with brilliant jerks and other difficult people as well as picking your battles in general.
Lastly, we appreciate a lesson on how to deal with legacy organizations that embrace innovation mostly verbally.
Food for Agile Thought’s issue #131—shared with 15,032 peers—focuses on how to make agile happen in large organizations: who will most likely kick-off a successful adoption, how to embed ‘experimentation’ in the culture, and why distributed teams do not exclude an organization from becoming agile.
We then get back to the challenge of ‘what to build.’ John Cutler shares a list of questions for product roadmap and prioritization issues, and we learn how to reduce the risk of creating an MVP with JTBD. Also, Alpha shared the results of its recent product management trends survey.
Lastly, we are invited to get a better understanding of Sociocracy 3.0 — one of the agile concepts left of the chasm.
Food for Agile Thought’s issue #130—shared with 14,911 peers—covers once more the corporate agile failure at legacy organizations. We like the guide to suitable agile metrics by XSCALE Alliance’s Leon Tranter, and we deal with how to scale and align a growing engineering team.
We then dive deep into the psychology of creating products: from confirmation bias, Kahneman’s systems 1 and 2, the benefits of listening to talking, persuasion techniques, to 25 cognitive biases.
Lastly, we remember the project management nightmare called ‘waterfall.’
Food for Agile Thought’s issue #129—shared with 14,709 peers—covers mental models relevant to your agile journey and shares the download link to an excellent book on team-centric agile software development. (Yub, it is free of charge.)
We then dive into organizational resilience through business agility, what your stakeholders want to know regarding your product roadmap, and why loving your customers’ problems will make your life so much easier.
Lastly, Intercom’s VP of Product created an overview what product people with an agile mindset can expect from the organization. (And the good folks at Intercom are checking a lot of the right boxes!)
