So excited for this conversation.  The time wasted on estimates and what leaders want to do with these makes my head hurt.  Waste vs having fruitful conversations are not the same

So - the issue, as in many cases - is poor leadership and weaponization of anttying that varies from a commit

I developed an risk-based conversation around ranking work items based on if they are kittens (little to no risk), exploding kittens (where you share any risk), and fat cat (because it could "have kittens" or go on a scope diet). From there we talk about diffusers. This has been much more interesting and focused on getting the team on the same page vs. pointing.

Squirrel and Jeffrey have different takes on the value of estimating a tech team's planned work at the beginning of a longer cycle, like a sprint or a quarter: Jeffrey says the discussion of an estimate often leads to insights and better outcomes, and Squirrel says you can get the same results without the estimates. Both agree that sharing and measuring against the estimates outside the team is counterproductive!

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

---

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 I

A bit of festive magic for you. 

We have invited Marcin Floyran and Sebastian Lambla back onto the podcast to discuss VeST (Vertical Slice Technologies). They were last on the podcast about two years ago to talk about Agile Anarchy and we asked them back to talk about VeST. So here it is. Aslak is asking the questions. 

This is a great listen for those who are interested in building customer-centric, high-quality software products.


Topics discussed during the podcast include:

 - The core concepts of VeST and its benefits.

 - Why focusing on the customer can be a great first-step for teams steeped in legacy code.

 - Debunking hexagonal architecture and ports and adapters. 

 - The role of traditional testers and mob testing. 

Shownotes

 - Sebastian's blog - https://serialseb.com/serials/vest-redux/

 - Agile Anarchy podcast - https://cucumber.io/blog/2016/02/16/agile-anarchy

 - Kind of Green - Aslak's post about how we are building Cucumber Pro -https://sdjournal.org/bdd-like-jazz/

Shout out the pod on Twitter @cucumberbdd - https://twitter.com/cucumberbdd

VeST - Vertical Slice Technologies

This week, Jeffrey and Squirrel are on the road at CITCON Vienna, interviewing participants about how they use agile techniques and principles outside development.

SHOW LINKS:

-The 12 Agile Principles: http://agilemanifesto.org/principles.html

-CITCON: http://citconf.com/

-London Organisational Learning Meetup: https://www.meetup.com/en-AU/London-Action-Science-Meetup/

***

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

Email us: agile@troubleshootingagile.com

Tweet us: twitter.com/TShootingAgile

Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

Agile Outside Software Teams

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.

Estimates: A Productive Argument, Part I

Troubleshooting Agile

Recent comments

Kevin Rush

Geri Pohl

Geri Pohl

Related tracks