Food for Agile Thought’s issue #200—shared with 22,519 peers—delves into fixed agile, we learn about how large organizations assess a Scrum Master’s qualification, and why ‘agile transformation’ is not ideal as a story to tell.

We also ask whether all of your organization’s members can answer the “what is your product” question consistently, we gain a better understanding how uncertainty will influence product discovery and delivery, respectively, and brush up our understanding of effective Product Backlog refinement techniques.

Lastly, we like to thank Basecamp for providing another free webbook on software project management Basecamp-style. (#NoAgile, #NoScrum, #NoWaterfall, #NoPostits, #NoSprints, #NoStandups — just saying.)

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

Food for Agile Thought’s issue #199—shared with 22,476 peers—analyzes the Boeing 737 MAX debacle from a software quality perspective; we delve into fixing Scrum by starting with proper working agreements, and we listen to a software architect who believes that his role is compatible with the Manifesto.

We also reflect on the “go wide, narrow, go wide, narrow” rhythm of Design Thinking, we build apps without coding, and we ask: should prioritization and the product roadmap be a job of the product team?

Lastly, we finish with a more technical, yet fascinating topic: mob programming patterns!

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