structured freedom with rules and strategies
DESCRIPTION
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.TRANSCRIPT
Structured Freedom with Rules & Strategies
Prabhakar Karve
In Our Session Today..
Your expectations
Help meet challenges of agile leadership
Simple generic solutions - not tips & tricks
Outline
Introduce rules & strategies
Agile success factors - Leadership challenges
Manage rules - support strategies
Organizational structures & effect on freedom
Q&A
2
Rules and Strategies
3
Rules and Strategies
Rules
Created by few – Followed by many
Follow – or face the consequences
Purpose or reason of creating any specific rule
Welcome – or oppose
Beliefs/ Preconceived notions
Strategies
Created by all – For themselves
No direct consequences
Specific situation or context
4
Rules and Strategies
Rules -> Strategies
To subvert rules
To replace rules
Can co-exist with rules
5
Priorities For This Decade
Key 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
Enhanced quality
“Done” within short iterations
Specific roles & responsibilities
Significantly different vis-à-vis traditional methodology
Self-organizing Culture
Supported by self disciplined teams
Leadership Challenges
7
How are we doing so far?
Manage Rules
Support Strategies
8
Quality
“Done” within short iterations
Scrum as a container for best practices
Requirement readiness
Change in code - test sequence
9
Roles & Responsibility
Clear-cut responsibilities and authority
As rules for incumbents
Who support each other
Need strategies for all others
10
Self-organizing Culture
Needs self-disciplined Teams
“Can do” belief
Progressive empowerment
Collaborate, learn and share
11
General Guidelines
Rules
Avoid too many rules
Scrum rules & org rules
Periodically review for relevance
Strategies
Document the context
Build a good repository
12
Structures and Freedom
13
Structures
Assumption - 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
Structure Types
Hierarchical Structures
Power structures
Communication channels
Legal Structures
Policies procedures & standards
Automation & tools
Cultural Structures
Traditions and conventions
Peer pressure
15
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
Agile leadership
Scrum teams
Work closely with Scrum masters
Progressively transfer control to the teams
Strategies to integrate other stakeholders
Organization
Repeat strategies to create processes
Watch structures - calibrate rules
17
Questions
18
Thank you