Thoughts on “consistency” in ways of working

Consistency can be imposed or natural.

  • Impose consistency through policy;
  • Encourage consistency naturally via exposure.
  • Having showcases between teams about how they do things and ideas they have;
  • Rotating people between teams;
  • Combining multiple teams into one team.

Consistency is not universally good or bad.

Consistency is most important with interaction protocols.

  • Agree clearly on how we will work together;
  • Agree what decisions are made across teams and what decisions are delegated to within a specific team

--

--

--

Staff Agile Coach at Spotify, ex-ThoughtWorks, ex-CruiseControl

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

C# : Custom Classes and Constructors

Clipping Images with CSS

Conclave Beta is here

🔅Automating LVM Partition using Python-Script.

ARKit 911 — A full list of AR classes

Add a Gravatar Image Lookup To Your FileMaker App

Gravatar fmIgnite Starter

Plotting changing results over distance with python

Public Protected Private Modifiers in Java

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Jason Yip

Jason Yip

Staff Agile Coach at Spotify, ex-ThoughtWorks, ex-CruiseControl

More from Medium

The top 3 points you should have paid attention to in the Spotify Engineering Culture videos that…

Alignment vs autonomy in a 2x2 matrix

Stop the Snowball

The work-in-progress falacy and the power of WIP limits

Modern working practices