4. • Component BasedTeams (700+ engineers)
• 12+ months waterfall releases
• Limited exposure to business
• 50+ features per release
• Branch based development
• Cross functionalTeams (50+ scrum teams)
• Scrum based quarterly releases
• Dedicated SM and PO Role
• CustomerValidation at the end of each sprint
• Continuous Integration – No branches
4
APG | Big Bang …
5. Conflict
Team Demotivated
Mired in Bureaucracy
& Wasted Effort
Energy &
Innovation
Team Trusted
Team Accountable
Leader Freed
Failure
No One Cares
Command &
Control
Team Does as Instructed
No Ownership
Leader / Process
is Bottleneck
HighTeam/Individual Ownership
Control
Trust
Low
Leadership
&BusinessProcess
APG | Once we started our journey …
6. 6
2
1
3
4
Agile Enthusiast’s leap of faith
CreateAgile PracticeGroup
Top leaders’ support
Continuous Support from Sr. Management
Self Motivated SMs
Started team with 3 motivated SMs
Started September 2014
And still going strong
APG | Origins …
7. APG
Learning
Continuous Learning
To Manage Change
• Mindset
• Organizational
• Leadership
Consistency
Consistent Principles
Communication
Shared Understanding
Protection
Independent VoiceAPG |Why do we need APG …
11. xx
Weekly
meeting
1 SM 2Teams
Epic CoreTeam SM
Initiatives
Non-negotiable
APG meeting
Quarterly
Planning
Anonymous
Surveys
Learn
Teach
Learn
Focus Groups
APG | Operating Model …
12. Teams missing MVP
Complete Dates
Lack of clarity on
remaining work
Ineffective dependency
tracking
Misaligned Priorities
APG | Challenges, couple of big ones …
Predictability