Structured freedom with rules and strategies


Published on

Agile is about self-organizing, empowered teams. More freedom is expected than what traditional project management offers. Leaders have a challenge to balance this freedom with need for predictable outcomes. Rules are mandatory; strategies are optional. Rules provide stability & continuity, while strategies help adapt to different situations. Too many or wrong rules diminish freedom. Too few and we are in danger of losing control. The session introduces concept of Structured freedom and explains with examples how the right balance between rules and strategies can be achieved.

Published in: Business, Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Structured freedom with rules and strategies

  1. 1. Structured Freedomwith Rules & Strategies Prabhakar Karve
  2. 2. In Our Session Today..Your expectations  Help meet challenges of agile leadership  Simple generic solutions - not tips & tricksOutline  Introduce rules & strategies  Agile success factors - Leadership challenges  Manage rules - support strategies  Organizational structures & effect on freedom  Q&A 2
  3. 3. Rules and Strategies 3
  4. 4. Rules and StrategiesRules Created by few – Followed by many Follow – or face the consequences Purpose or reason of creating any specific rule Welcome – or oppose Beliefs/ Preconceived notionsStrategies Created by all – For themselves No direct consequences Specific situation or context 4
  5. 5. Rules and StrategiesRules -> Strategies To subvert rules To replace rules Can co-exist with rules 5
  6. 6. Priorities For This DecadeKey success factors for agile movement Demand technical excellence Promote individual change and lead organizational change Organize knowledge and encourage education Maximize value creation across the entire process 6
  7. 7. Leadership Challenges Enhanced quality  “Done” within short iterations Specific roles & responsibilities  Significantly different vis-à-vis traditional methodology Self-organizing Culture  Supported by self disciplined teams How are we doing so far? 7
  8. 8. Manage RulesSupport Strategies 8
  9. 9. Quality“Done” within short iterations Scrum as a container for best practices Requirement readiness Change in code - test sequence 9
  10. 10. Roles & ResponsibilityClear-cut responsibilities and authority As rules for incumbents Who support each other Need strategies for all others 10
  11. 11. Self-organizing CultureNeeds self-disciplined Teams “Can do” belief Progressive empowerment Collaborate, learn and share 11
  12. 12. General GuidelinesRules Avoid too many rules Scrum rules & org rules Periodically review for relevanceStrategies Document the context Build a good repository 12
  13. 13. Structures and Freedom 13
  14. 14. StructuresAssumption - What works today will work in the future Structures evolve by repeated use Habit forming  Once formed difficult to change Useful structures help streamline work  Harmful structures create roadblocks 14
  15. 15. Structure Types Hierarchical Structures  Power structures  Communication channels Legal Structures  Policies procedures & standards  Automation & tools Cultural Structures  Traditions and conventions  Peer pressure 15
  16. 16. Freedom Agile teams need greater freedom Structures help as well as hinder freedom Mature self-disciplined individuals  Need and handle greater freedom Progressive empowerment 16
  17. 17. Agile leadershipScrum teams Work closely with Scrum masters Progressively transfer control to the teams Strategies to integrate other stakeholdersOrganization Repeat strategies to create processes Watch structures - calibrate rules 17
  18. 18. Questions 18
  19. 19. Thank you