Autonomy is a cornerstone of agile transformation. However I’ve seen it taken the wrong way too.<\/p>\n
IMHO, autonomy means:<\/p>\n
– Self organizing teams who don’t have to wait for someone to take decisions on their behalf<\/p>\n
– Who have the autonomy to estimate work (within reasonable guidelines) and drive decisions related to completing the work<\/p>\n
– As they can take technical decisions, so are they responsible for those solutions – you code it, you own it<\/p>\n
What it does NOT mean:<\/p>\n
– Create a bubble and make sure no one from the outside has any visibility into the working of the team (no one can come to our stand ups \/ retros or other ceremonies). Agile is about transparency remember!<\/p>\n
– Take autonomy as a ‘do whatever and get away with badge’ – for example, give unrealistic estimations and having no technical reasoning for why it’s going to take that long.<\/p>\n
A big factor in all this I guess is having a purpose and being driven also.<\/p>\n
And make no mistake – this will have a direct impact on quality of your product – and hence should be factored into the KPIs to measure.<\/p>\n
What is your experience on autonomy in teams?<\/p>\n<\/div>