Following last week's debate, Squirrel and Jeffrey share their different takes on the value of having estimated a tech team's planned work when it comes to a retrospective at the end of a cycle, like a sprint or a quarter: Jeffrey sees that checking what the team achieved against what they planned can lead to important lessons about dependencies, inefficiencies, and skills gaps, while Squirrel thinks the risk of the estimates "escaping" is too high, and that the team ought to be able to notice process failings as they go without the "crutch" of estimates. 

SHOW LINKS:

- LinkedIn post: https://www.linkedin.com/posts/dsquirrel_my-friends-at-cto-craft-are-45-right-about-activity-6983761206993899522-raHE

- Squirrel Tweet: https://twitter.com/douglassquirrel/status/1578315480472985602

- You’re Not So Smart : https://www.davidmcraney.com/new-page-1

---

Our book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list!

We'd love to hear any thoughts, ideas, or feedback you have about the show.

Email us at info@agileconversations.com

Estimates: A Productive Argument, Part II

Troubleshooting Agile is a problem-solving session for agile teams. Jeffrey Fredrick and Douglas Squirrel look at common problems agile teams face and provide practical, immediately useful advice for getting back on track.