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

Turning our usual subject on its head, this week we start a short series on how to make sure your team does NOT improve. The first assumption to this end: the belief that you understand the situation while others don't. The change that's needed is obvious; all you have to do is convince others to adopt it. Easily adaptable to kanban, scrum, SAFe, or any other method that seems (to you!) to be the solution to your problems. Try it today, and tune in to further episodes for more ways to ensure you don't succeed in making effective changes!

SHOW LINKS:

- How Unilateral Control Undermines Team Results and Relationships, Schwarz: http://www.schwarzassociates.com/managing-performance/how-unilateral-control-undermines-team-results-and-relationships-2/

- Naive realism: https://en.wikipedia.org/wiki/Na%C3%AFve_realism 

***

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

Email us: see link on 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: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

How to Fail by Acting Unilaterally - Part I

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.

How to Fail by Acting Unilaterally - Part I

Troubleshooting Agile

Related tracks