This document discusses rules and strategies for agile leadership. It introduces rules and strategies, noting that rules are created by few and followed by many with consequences, while strategies are created by all for specific situations. Rules can be subverted, replaced, or coexist with strategies. The document outlines priorities like demanding technical excellence and organizing knowledge. It discusses leadership challenges like ensuring quality, clear roles and responsibilities, and self-organizing culture. It suggests managing rules to support strategies. The document discusses how structures can help and hinder freedom, and how agile teams need freedom but also self-discipline to handle it.
4. 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
5. Rules and Strategies
Rules -> Strategies
To subvert rules
To replace rules
Can co-exist with rules
5
6. 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
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
9. Quality
“Done” within short iterations
Scrum as a container for best practices
Requirement readiness
Change in code - test sequence
9
10. Roles & Responsibility
Clear-cut responsibilities and authority
As rules for incumbents
Who support each other
Need strategies for all others
10
12. General Guidelines
Rules
Avoid too many rules
Scrum rules & org rules
Periodically review for relevance
Strategies
Document the context
Build a good repository
12
14. 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
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. 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. 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