Improving velocity through better communication
•Download as PPTX, PDF•
0 likes•250 views
Talk given at the Clearvision conference: "The Future of Team Collaboration" Discusses how improving the way that your team communicates with Agile and DevOps will increase the velocity of your organisation and help make systems safer and more reliable.
Recommended
More Related Content
What's hot
What's hot (19)
Similar to Improving velocity through better communication
Similar to Improving velocity through better communication (20)
Recently uploaded
Recently uploaded (20)
Improving velocity through better communication
- 1. Peet Denny LV= Principal Architect Velocity Through More Effective Communication or ‘How To Make More Awesome In Less Time’
- 2. Velocity The ability to turn ideas and funding into reality at speed
- 3. Ideation Funding Design Build & Test Ship Value Traditional Delivery Pipeline Many months or years *Simplified and exaggerated
- 4. The Greatest Risk To The Project: It Won’t Ship You’re Building The Wrong Thing: • Working on incorrect assumptions • Don’t understand the customer • Don’t understand the business stakeholders • Haven’t considered all of the constraints • Tricky non-essentials crowd out the MVP http://amzn.to/1lpAYsZ
- 5. Ideation Funding Design BuildShip Value Learn A Few Weeks Daily Team Interactions Iterative Delivery Pipeline
- 6. How Do We Incentivize Our Teams? Dev: Incentivized for change Ops: Incentivized for stability
- 7. The Wall Between Departments 7 Don’t Underestimate the Beer Effect
- 8. Improving Quality Of Communication Create a safe environment for people to communicate It’s OK to fail and learn Creating a culture where sharing information (even about negative things) is desirable Design and code out in the open Design in confluence – early visibility invites critique GDS publish most code to public Github
- 9. Willingness To Speak About Failure Improves Safety Gladwell’s Ethnic Theory of Plane Crashes http://on.wsj.com/19NpHdp
- 10. Westrum’s “Three Cultures Model” Pathological (Power-oriented) Bureaucratic (Rule-oriented) Generative (Performance- oriented) Low cooperation Modest cooperation High cooperation Messengers shot Messengers neglected Messengers trained Responsibilities shirked Narrow responsibilities Risks are shared Bridging discouraged Bridging tolerated Bridging encouraged Failure leads to scapegoating Failure leads to justice Failure leads to inquiry Novelty crushed Novelty leads to problems Novelty implemented From ‘a typology of organizational cultures’ published in the British Medical Journal http://bit.ly/1RfpYuw
- 11. The Retrospective Prime Directive Regardless of what we discover, we understand and truly believe that everyone did the best job they could given what they knew at the time, their skills and abilities, the resources available, and the situation at hand
- 12. Re-cap Improve FREQUENCY of communication Improve QUALITY of communication Go FASTER over the long term @peetdenny
Editor's Notes
- In this model, team members are disconnected in terms of time, and therefore in terms of space too. This inhibits communication and encourages people to focus on their part of the process, rather than the mission itself.
- An agile approach with short sprints requires that everyone involved in the process be engaged during the same period. So at least from a temporal perspective, there is a team. Co-locating is even better, and ensures that communication is super frequent.
- Different teams can be incentivized to achieve different things. This is useful, because they *should* care about different things. However a better understanding between the teams will help all involved to club together to solve each other’s pain points
- This friction between differently-incentivized teams can be smoothed over by building personal relationships. This can be encouraged by getting people together socially. This is a less cynical way of putting Corleone’s idea of ‘keeping your enemies closer’
- The whole study is worth a read. But a great exercise to carry out here is to get the exec to each highlight independently which cell they think best describes the organization for each area. They will probably have different perspectives, which should cause some great debate. Nobody wants to think of their organization as Pathological or Bureaucratic, and yet many of us are, at least in some areas
- Read this out at the beginning of every retrospective to encourage people to speak their mind, own the criticism they give, and to not fear criticism of others.
- If you’d like me to give this talk at your organization, get in touch. I also do weddings and bar mitzvahs