Our posts by Stefan Wolpers

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 #183—shared with 21,403 peers—covers a new leadership health check tool by Crisp, InfoQ’s State of Practices report 2019—Liberating Structures made it onto the list—, and we analyze what ‘executive sponsorship’ means for change in reality.

We also address how to move from an output-minded to outcome-minded organization; we attempt to figure out whether there is an end to customer development and we warm up to a coaching tool for product managers looking for excellence.

Lastly, we dive into the issue that providing feedback does not seem to have a real impact on other people. What does that mean for retrospectives and self-organizing teams?

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

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?