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

Although we talk about joint design a lot, we haven't managed to do an episode on it. As we get to chapter 4 in our tour through Agile Conversations, it's time to rectify that! We focus on a common error that we didn't cover in depth in the book: how trying to "convince" someone through advocacy fails. Using the Four Rs, we roleplay an ineffective advocacy-heavy conversation about tech team execution, and then revise it to increase curiosity, reduce defensiveness and achieve greater internal commitment.

SHOW LINKS:

- Getting to Yes: https://en.wikipedia.org/wiki/Getting_to_Yes
- David Burns on (not) trying to help: https://feelinggood.com/2019/10/28/164-how-to-help-and-how-not-to-help/
- Previous episodes and blog posts on joint design:
   - https://soundcloud.com/troubleshootingagile/mutual-learning-model-part-one
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-i
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-ii
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-iii
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-iv 
   - https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-v 

Episode transcript: https://www.conversationaltransformation.com/posts/why-finding-the-balance-for-joining/

---

Our new book, Agile Conversations, is out now! See https://conversationaltransformation.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@conversationaltransformation.com

Why: Finding the Balance for Joint Design

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.

Why: Finding the Balance for Joint Design

Troubleshooting Agile

Related tracks