leadership lessons from scaling adobe’s cloud infrastructure...

© 2015 Agile For All. All Rights Reserved.

Leadership Lessons from Scaling

Adobe’s Cloud Infrastructure Team

Peter Green


Peter Green

•  Trainer, Coach, and Facilitator •  Launched dozens of teams on their successful agile transitions,

frequent team activity facilitator, experienced coach for Executives, Teams, and Individuals

•  2005-2015: Adobe Agile Transformation Leader •  Led Adobe’s adoption of a Lean and Agile approach from

2005-2015, a key enabler of Adobe’s shift to a rapid release subscription approach.

• Patent Holder •  U.S. Patents 8,600,529, 8,044,291, 8,352,052, International

Patent 1876597. •  In demand speaker

•  Multiple Adobe Tech Summits & Mini Summits, Agile Alliance Conferences, Scrum Gathering Conferences, Agile Roots, and HICSS conferences

• Published author •  IEEE Journal & case studies in books by Ken Schwaber, guest

blog posts for Mike Cohn and others • Certified Scrum Trainer

•  Trained 1000s of CSMs & CSPOs •  Instructional Designer

•  Courses in Scrum, Lean, Lean Startup, Agile Product Management, Agile Coaching & Facilitation, and Agile Leadership


Adobe’s Scrum Adoption

2005

2015


Adobe Photoshop

Peak bugs reduced to 12% of previous cycle

Adobe After Effects


Bug Curves Before & After Scrum

4

Adobe Premiere Pro


Adobe Flash Pro


Adobe Audition



Feature Council Plays the Product Owner Role

Scrum Team Builds a related set of features

Typical Adobe Product Team

PO

SM

UX

ENG QA


Identity

Entitlements

Storage

Shared Cloud Infrastructure Team


Why Spotify Approach?

7

Server

Client Application

Database

Server Team 2

UI Team 1

Database Team

Server Team 1

UI Team 2

Server

Client Application

Database

Squad 1

Squad 2

Squad 3

Squad 4

Squad 5

Cross-team coordination required for: §  Value delivery §  Most Dependency Management §  Debugging Customer Problems

Cross-team coordination required for: §  Technical knowledge sharing §  Some Dependency Management

Team Responsibility:

Technology Stack Delivery Team Responsibility:

Customer Value Delivery


How Spotify Does It…

8


Moving To Squads

1.  Hamburg 2.  San Jose 3.  Seattle


Shared Cloud Infrastructure Team

Lessons: 1. Pull, not push 2. Honest Answers 3. Leadership Enrollment 4. Build a coalition


Why It’s Hard, Why It’s Worth It

•  Mindset > Practices

•  Big Change = Large Quantity of Conversations

•  Leadership Enrollment

Probably Hard Because:

•  Clear Squad Missions

•  Clear Roles

•  Reduced Dependencies

Might Be Worth It Because:

leadership lessons from scaling adobe’s cloud infrastructure...

Documents