Food for Agile Thought’s issue #158—shared with 18,935 peers—visits the poster child of self-managed organizations—Semco—, we deal with building trust in teams, and we learn why agile companies no longer require plans.
We appreciate Roman Pichler’s sprint planning tips & tricks for product owners, we dive into the commandments of outstanding products, and we understand how falling in love with a solution can wreck a whole organization.
Lastly, we come back to product discovery and learn a new approach how to reinvent a strategy to figure out what’s worth building.
Food for Agile Thought’s issue #157—shared with 18,862 peers—applauds Martin Fowler for his Agile Australia keynote on Agile 2018, we learn about the road to mediocrity, and we ask: Is the Peter Principle not a satire but reality?
We also address the issue of hidden (technical) costs of being ‘agile,’ as well the how to solve the conflict between prioritizing business needs as well as maintaining the health of the code base.
Lastly, we deal with the challenges of planning poker in a short and entertaining video.
Food for Agile Thought’s issue #156—shared with 18,778 peers—focuses on servant leadership, why change cannot be rushed, and how one road to enterprise business agility may look like.
We also have a look at mental models for product managers/owner; we learn how free time from our schedules to run user interviews regularly, and how to avoid failure when reaching for product/market fit.
Lastly, we like to thank Bartosz for compiling a great list of resources to help us to apply servant leadership in the trenches. 🙏
Food for Agile Thought’s issue #155—shared with 18,683 peers—focuses on effective team building, how agile data can support your storytelling during an agile transition, and why the change agent needs to be ahead of the game at any time.
We also have a look at the silent estimation technique and why it may replace planning poker, and why professional product backlogs have the shape of an iceberg.
Lastly, we ask ourselves: is ‘lean startups’ probably nothing more than a failed ideology, a useless tool if your organization is looking to improve its innovation game?
Food for Agile Thought’s issue #154—shared with 18,591 peers—focuses on agile’s many faces, be it the progress of business agility, mob programming, or descaling the organization to ‘scale agile.’
We also have a look at Scrum.org’s brand-new advanced scrum master class, and share a reading tip — Jez Humble’s recent book on building and scaling high-performance technology organizations is eye-opening.
Lastly, we applaud Peter Casinelli who advocates that developers should conduct user tests, we learn six principles of modern product discovery, and we take to heart that no one is immune to cognitive bias.
Food for Agile Thought’s issue #153—shared with 18,517 peers—focuses on agnostic agile as a critical element for successful agile transitions and the havoc a dogmatic use of any of the agile frameworks may cause. Which leads to the question of whether we need all the ceremonies anyway? (There is a Spotify experiment that may help to answer this question.)
We also get back to team building—starting from scratch or starting over—, and we cherish a free book on continuous innovation from InfoQ.
Finally, we address the odd couple again—(UX) design and agile—and try to make things work for everyone.
