Agile

DevOps

Organizational culture & cross functional teams are critical ingredients for rapid and secure releases

The best processes in the world are meaningless unless you have an effective teaming structure and enabling culture. The setup and use of cross functional teams (x-teams) has long been researched and documented as a way to overcome organizational challenges with silo mentality, issues of waste and speed caused by the challenges of complex environments and work handoffs.  

These principles and practices are reflected in Lean’s use of Kaizen improvement teams, Agile’s borrowing of the Rugby Scrum team model and now DevOps is leveraging these principles in what has been referred to as a DevOps Team. However this concept was not invented by these movements but has been adopted to deal with challenges which impact all IT functions that work within complex systems.

Join George and I in this entertaining podcast as we discuss this topic with our special guest J. Paul Reed who is a Release Engineer and an early pioneer in the DevOps community.

Dan's Album

PR 70 - Release Management & DevOps Teams

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Sanjeev Sharma, a Distinguished Engineer at IBM, on the challenges for large enterprises adopting DevOps at scale and what it really means to have a DevOps culture

Why listen to this podcast:

•	There is no single “why” for adopting DevOps – each organisation is unique and the adoption approach should be based around what they are trying to optimize
•	DevOps is not a methodology – it is a set of guiding principles 
•	As more and more parts of the business get to the higher levels of maturity you get to DevOps adoption at scale
•	The biggest challenge to adopting DevOps in a large enterprise is overcoming cultural inertia
•	The cultural impact of DevOps needs to be about building trust across silos in the organisation 
•	There is a need for DevOps coaches who have skills that go deep into the operations areas, not just rebranded Agile coaches
More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2wmiDEv

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Check the landing page on InfoQ: https://bit.ly/2wmiDEv

InfoQ Podcast

Show Notes

Sanjeev Sharma of IBM on what a DevOps Culture Really Means

Created in partnership with CIO from IDG, episode 4 of the cloud automation podcast series explores whether companies should be preparing to go beyond DevOps and adopt NoOps methodology.
Cloud automation and DevOps are already transforming IT for many enterprises and making their operations more efficient. Now, however, some enterprises are taking this concept one step further by completely automating the deployment, monitoring and management of applications, as well as the underlying infrastructure that supports them. In theory, you could run applications and services without any operations whatsoever. But the question remains: Is it practical?

Visit (goo.gl/cqpUmz) to learn more.

Speakers
•	Ben Scowen (twitter.com/bescowen) – xPaaS Business Lead, Capgemini Cloud Platform 
•	Stuart Ball (https://uk.linkedin.com/in/stuart-ball-a352884) – Vice President
•	Charlotte Jee, Technology Journalist

Cloud automation: Episode 4 - DevOps or NoOps: Which is the future?

As promised, we start describing our favourite trust-building technique: the Ladder of Inference. Our take this week is on using the Ladder to understand someone else's reasoning and align your stories, creating trust as a foundation for further improvement in your agile team. Surprisingly, the experience of using the Ladder in this way is similar to Test-Driven Development: careful, understandable, small steps with confidence, and meaningful signals from both success and failure.

SHOW LINKS:

- Peter Senge, The Fifth Discipline: https://www.amazon.co.uk/dp/B003ELY7OW/ref=dp-kindle-redirect?_encoding=UTF8&btkr=1 
- The Ladder of Inference (annotated by Jeffrey): http://troubleshootingagile.com/docs/TheLadderOfInference.pdf
- Cognitive biases book and more: https://youarenotsosmart.com/
- Schwarz on unilateral control (again!): http://www.schwarzassociates.com/managing-performance/how-unilateral-control-undermines-team-results-and-relationships-2/
- TDD for people video: https://www.douglassquirrel.com/how-i-work.html
- Schwarz 8 behaviours (Paula/Ted are on page 4): https://www.csu.edu.au/__data/assets/pdf_file/0008/917018/Eight-Behaviors-for-Smarter-Teams-2.pdf

***

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

Test-Driven Development for People

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.