In this week's Podcast we're on to the penultimate Agile Principle, number 11: 'The best architectures, requirements, and designs emerge from self-organizing teams.'

Amongst much more, we discuss:

-How what should actually constitute a team is the sharing of a problem, not a manager.

-The importance of employing a dynamic team approach, rather than a static one, to solving problems.

-How the unique specificity of this principle is designed to get us away from the old 'phase' approach and avoid costly hand-offs.

-Specific techniques to inspire a mutiny and become a self-organizing team, with some lessons from Stephen Bungay's 'The Art of Action', such as how to employ Direct Opportunism.

-The Spotify model and the importance of shunning the easy route of adopting an off-the-shelf model.

***

SHOWNOTES:

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

-Alistair Cockburn's mighty fine Koan for Agile development:

"Management tells the workers to mutiny.

The workers refuse"

http://alistair.cockburn.us/Self-organization+means+mutiny

-Stephen Bungay's brilliant book, 'The Art of Action': https://www.amazon.co.uk/Art-Action-Leaders-between-Actions/dp/1857885597/

-The unique case of the General Electric plant in Durham, North Carolina:

http://www.fastcompany.com/magazine/28/ge.html

-Spotify's self-organised teams, not an off-the-shelf model to copy: https://labs.spotify.com/2014/03/27/spotify-engineering-culture-part-1/

-Sign up to CITCON in Vienna, there aren't many spaces left: http://citconf.com/

***

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

Email us: [email protected]

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