Some Thoughts on Self-Organization in Agile Teams
Some Thoughts on Self-Organization in Agile Teams
Join the DZone community and get the full member experience.
Join For FreeAdopting a DevOps practice starts with understanding where you are in the implementation journey. Download the DevOps Transformation Roadmap. Brought to you in partnership with Techtown.
I think some of us are getting it wrong when it comes to self-organization.
Self-organization doesn’t mean that the team doesn’t have managers or that they get to decide what problems to solve or what product to build.
Self-organization doesn’t mean that the team doesn’t have any tooling constraints, or architectural constraints, or budget constraints, or timing constraints.
Self-organization doesn’t mean that the team decides who is on the team, how big the team is, or how much money everyone on the team should make.
Self-organization DOES mean that once the team is formed, and given a problem to solve, and a set of constraints to operate within, the team gets to decide how the work is done.
While any given team, in any given company, may have have latitude to make any or all of these decisions, in my opinion, that is not what is meant by self-organization as it pertains to agile.
I’m interested in your thoughts.
Take Agile to the next level with DevOps. Learn practical tools and techniques in the three-day DevOps Implementation Boot Camp. Brought to you in partnership with Techtown.
Like This Article? Read More From DZone
Published at DZone with permission of Mike Cottmeyer , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}