Autonomy in Teams - Why & How !
This is a fast paced workshop of 90 minutes, split across 3 progressive parts/activities. The intent of the workshop is to bring out the challenges that organizations face due to their traditional structure, during their Agile adoption journey. In the workshop, we emulate such an environment and try to have a first-hand experience of the difficulties faced both at the team and managerial levels (Part A). Subsequently, we let people form their own teams which are "Autonomous". (Part B). Now, we deliver as newly formed teams. (Part C).
The final debrief revolves around importance of "Autonomous teams" in terms of quality and individual motivation.
Outline/Structure of the Workshop
1. Introduction & stage setting (5 mins)
2. Part A - delivering as "vertically-structured" organization (15 mins)
3. Debrief of Part A (5 mins)
4. Part B - Self-forming, Autonomous team activity (15 mins)
5. Part C - delivering as "horizontally-aligned" organization (15 mins)
6. Final Debrief (5 mins)
1. How "vertically-structured" organizations find hard to be Agile.
2. Mindset needed to begin from being "vertically-structured" to "horizontally-aligned" organization.
3. How "Autonomy in Teams" can be the best kind of intrinsic motivation.
Coaches, Managers, Developers
schedule Submitted 5 years ago
People who liked this proposal, also liked:
Devesh Chanchlani - Branching for Continuous Delivery? Think Again!Devesh ChanchlaniConsultantSteerlean
schedule 5 years agoSold Out!
Effective "Code-branching" strategies are still one of the most ignored in Agile development world. In this talk, using case-studies, I would like to present what is wrong with traditional strategies, how it hinders teams to deliver continuously and why Trunk Based Development (TBD) is a durable solution. Furthermore, the talk aims to explore various strategies (code/dev and ops) that enable teams to attain TBD. Finally, the tealk ends with successful TBD case-studies of Facebook and Google.