Food for Agile Thought’s issue #185—shared with 21,547 peers—covers agile values and the path from project to product-focused organizations. We also learn what to look for when hiring agile teams, and take away lessons learned along the way of becoming an acknowledged agile coach.

Moreover, we address the rationale behind splitting user stories, how to deal with customer churn effectively from a learning perspective, and why ‘done’ tends to clash with ‘validated’ so often when engineers talk to UX folks.

Lastly, we enjoy a new book—available for free as a PDF—that takes a look at what the values of the Agile Manifesto mean when you try to apply them to work and life.

Did you miss last week’s Food for Agile Thought’s issue #184?

Food for Agile Thought’s issue #184—shared with 21,451 peers—covers eight winning agile management trends, we dive into waste in software creation, and we learn why Microsoft prevailed where General Electric failed.

We also address how to place a growth mindset at the core of your product strategy; we bring clarity to what data-driven means, and we applaud fyi for curating an enormous list of free product management resources.

Lastly, we bust trust building myths when you are in a leadership position—be surprised by the data!

Did you miss last week’s Food for Agile Thought’s issue #183?

Food for Agile Thought’s issue #182—shared with 21,278 peers—addresses the agile-industrial complex, the stages of progress in becoming agile—provided your organization belongs to the lucky few—, and the state of Cynefin in 2019.

We also learn more on how to deal with complaints that your user stories are not detailed enough—and why it is worth to get to the ground of this notion—; why strategy maps are essential to building valuable products, and how to Marie Kondo your product backlog.

Lastly, we understand why capability maturity models are unsuited for assessing any form of agility.

Did you miss last week’s Food for Agile Thought’s issue #180?

Food for Agile Thought’s issue #181—shared with 21,092 peers—addresses transparency, the lack thereof and other forms of dark agile. Moreover, we get a backstage view at the Scrum Master Trends Report, and we borrow from Atlassian’s team health tool.

We also get some new ideas about how to create product reviews people like to participate in; we refresh our memory why the traditional governance approach is unsuited for ’agile,’ and embrace the idea that product launches do not have to be a troublesome thing.

Lastly, Ron Jeffries asks what the agile community can do to reach out to those practitioners who haven’t yet experienced the real thing as outlined in the Manifesto for Agile Software Development. What are your thoughts?

Did you miss last week’s Food for Agile Thought’s issue #180?