TL; DR: Decision Making, Technical Debt Explained — Food for Agile Thought #268
Welcome to the 268th edition of the Food for Agile Thought newsletter, shared with 28,041 peers. This week, we delve into the dirty secrets of decision making; we refresh our memory regarding eight agile estimation practices, and we take appreciation beyond the usual Kudo cards.
We then welcome eleven lessons on how to escape the build trap; we come back Lean’s four phases of a product’s lifecycle, and we learn more about the results of evaluating an app in a real-life context.
Lastly, we embrace another approach to understanding technical debt.
TL; DR: Scrum Sprint Planning Checklist
A Sprint Planning checklist? How dare you: Agile is a mindset, not a methodology. It is a journey, not a destination. There is no one-size-fits-all approach, and what else could you possibly cover with a checklist, the mother of all standardized processes?
Well, it always depends on the purpose of a tool’s application. Read more about why Scrum checklists are a handy tool if applied at an operational, hands-on level, reduce your cognitive load, and free up time for more relevant things.
TL; DR: Psychopaths and Narcissists, Get Your Brain Back — Food for Agile Thought #267
Welcome to the 267th edition of the Food for Agile Thought newsletter, shared with 27,937 peers. This week, we learn how to deal with psychopaths and narcissists as a change agent; we move away from command & control to bring back creativity, and we figure out how agile contracting with customers works at an agency.
We then address eighteen product management paradoxes; we learn about eight avoidable mistakes when running experiments, and we get an overview of the results of a recent survey on OKRs and how organizations apply them in practice.
Lastly, we enjoy listening to Mary and Tom Poppendieck, sharing their thoughts on Lean as “a way of thinking that values people.”
TL; DR: 20 Questions from New Scrum Master to the Development Team
From Scrum Master to Development Team members, this set of questions addresses the foundations of a Scrum Team capability to build valuable products: technical excellence and what it takes to achieve this proficiency level. The questions have been modeled after some basic principles that high performing teams have in common—from keeping technical debt at bay to collaboratively creating a Product Backlog.
Download a printable template for your convenience.
Welcome to the 20 Questions from Scrum Master to the Development Team Download Page
From Scrum Master to Development Team members, this set of questions addresses the foundations of a Scrum Team capability to build valuable products: technical excellence and what it takes to achieve this proficiency level. The questions have been modeled after some basic principles that high performing teams have in common. Download a printable template for your convenience.
TL; DR: Popular Component Teams, Team Morale in WFH Times — Food for Agile Thought #266
Welcome to the 266th edition of the Food for Agile Thought newsletter, shared with 27,841 peers. This week, we attempt to understand the why and how of popular component teams; we choose new practices to build team morale remotely, and we confront our anxiety of having to deal with emotional reactions at work.
We then mourn the passing of product roadmaps (just kidding, they’re alive and well); we have a look at Spotify’s new platform supporting product discovery, and we gain a better understanding of how to determine the pricing of a SaaS product.
Lastly, we enjoy reading another free chapter of “The Art of Agile Development, Second Edition.”