This document discusses strategies for transforming a large organization to an agile methodology. It recommends starting with a "big bang" approach, where all teams transition together using Scrum. The transformation is driven from the top down but implemented bottom up. Teams are reorganized into self-organizing cross-functional teams with dedicated resources. The transformation focuses on iterative development, continuous delivery, and establishing core values like transparency. Coaching and training help drive adoption. Initial results include improved productivity, predictability, and executive buy-in. Advice includes focusing on principles over mechanics and getting early engineer involvement.

5. Smart

6. Fast

7. Crea+ve

8. Why
change?

9. Productivity
Cycle times

10. Unpredictable completion of anything

11. Lack of
Visibility

13. Resource
Bottlenecks

14. Dependencies

15. Enterprise customers
Trust is #1
Millions of Users
Intense corporate culture
Strong exec presence
Monolithic architecture
One delivery mechanism
65 Feature teams

16. Breakout Session
Unpredictable
Lack of visibility
Lack of responsiveness, priorities
Resource bottlenecks
Dependencies

18. Big Bang
Agile Transformation

19. Self-organized teams
Dedicated resources
Iterative
Time-boxed
Prioritized
Minimal Work-in-progress
Continuously Releaseable
Automation
Lean
Agile

20. Top Down decision: bottom-
up transformation
Vision, Values, Methods
Return to core values
Everyone jumps in together
Use Scrum to rollout Scrum
Transforma+on
Strategy

21. Rollout Scrum Team drives
Distributed Ken Schwaber’s
Scrum book
2-hour Agile overview
30 ScrumMasters to
ScrumMaster Certification
35 Product Managers to
Product Owner Certification
External Coaches
Execu+on

22. Results

23. Immediate impact
Hyper productive
Predictable

24. Executive buy-in
Principles over mechanics
Get several teams to excellence
Provide radical Transparency
Involve engineers early
Get outside coaching
Give executives deliverables
When the heat is on stick to your guns
Big
Bang
Advice

28. Values

29. Culture
&
Community

30. Hackweek

31. Hackweek

32. Hackweek

33. Hackweek

34. Hackweek

35. Hackweek

36. Hackweek

37. Hackweek

38. Growth
Throughput
Predictability

39. Consumer Internet
100’s of Millions of Users
Hacker culture
Engineer empowerment
Distributed services
Continuous deployments
Local deployment ownership
Individual bias

40. Top to Bottom
Invitation (no mandate)
No prescriptive methodology
Standards
Distributed Coaching
Evangelize
Strategy

41. Cross org visibility
Rhythm
Prioritization
Dependencies
Automation
Standards
Office Hours
Execu+on

42. Experiment
Involve engineers early
Tools agility
Principles over mechanics
Get several teams to excellence
Provide radical Transparency
Hacker
Agile
Advice

44. Thank you.
@xsgreene