SCALING AGILE IN A LARGE MATRIXED ORGANIZATION. Jen Krieger Chief Agile Architect Products & Technologies May 2017

Size: px

Start display at page:

Download "SCALING AGILE IN A LARGE MATRIXED ORGANIZATION. Jen Krieger Chief Agile Architect Products & Technologies May 2017"

Bertram Ferguson
5 years ago
Views:

1 SCALING AGILE IN A LARGE MATRIXED ORGANIZATION Jen Krieger Chief Agile Architect Products & Technologies May 2017

2 WHAT DOES IT MEAN TO SCALE AGILE? For the sake of brevity, we ll focus on Scrum as the methodology

3 2 weeks x2 5-7 (+/- 2) x3 Production xn

4 IS THAT PRACTICAL?

5 Requirements Prod Prod Prod Release Prod

6 Requirements Prod Prod Release Agile DevOps Prod Prod

7 I mud hike and bees mannish?! I would like a cheese sandwich. By Biblioteca de la Facultad de Derecho y Ciencias del Trabajo Universidad de CC BY 2.0 via Wikimedia Commons

8 WHAT DOES THAT LOOK LIKE IN PRACTICE?

9 CASE STUDY #1 Growing pains By Jean Beaufort CC0 Public Domain

EARLY TEAM CHARACTERISTICS circa 14 8 Hybrid Scrum Teams 2 Week Sprints 6 Week Releases to RHEL AH 60 Engineers 5 QE Engineers 1 Release Engineer 1 Architect 2 Agile

10 EARLY TEAM CHARACTERISTICS circa 14 8 Hybrid Scrum Teams 2 Week Sprints 6 Week Releases to RHEL AH 60 Engineers 5 QE Engineers 1 Release Engineer 1 Architect 2 Agile Coaches 1 Product Manager 5 Hybrid Scrum Teams 3 Week Sprints ~6 Month Releases to Enterprise 40 Engineers 12 QE Engineers 1 Release Engineer 1 Architect 4 Product Managers

SEPARATE PROGRAMS DIFFERING RELEASE CYCLES OPENSHIFT Developer Experience Platform

11 DETAILED VIEW PROJECT ATOMIC Containers Kubernetes End-to-End Integration Usability Red Hat Enterprise Atomic Host Atomic Host Storage Scale & Performance Internal Tooling TWO SEPARATE PROGRAMS DIFFERING RELEASE CYCLES OPENSHIFT Developer Experience Platform Management Productization OpenShift Enterprise Integration Services User Interface Online OpenShift Online

12 POST-MERGE TEAM STRUCTURE circa 15 ATOMIC OPENSHIFT Group 1 Building Blocks Cluster Infrastructure Containers Networking Platform Infrastructure Storage Usability Group 2 Origin Developer Experience Integration Services Platform Management User Interface Group 3 Product Online Productization e2e Product Integration Scale & Performance Internal Tooling Red Hat Enterprise Atomic Host OpenShift Enterprise OpenShift Online OpenShift Dedicated

13 CASE STUDY #2 By eliminating one bottleneck, we exposed some more. By Jean Beaufort CC0 Public Domain

SOME MORE BUMPS IN THE ROAD ATOMIC OPENSHIFT

!! Too many people in common meetings Group 1

! I can never get time with the architects!

! I have time to help, but don't know how.

Cluster Infrastructure Containers Networking

on Developer Experience There are Integration

products There are not enough people on this

14 SOME MORE BUMPS IN THE ROAD ATOMIC OPENSHIFT Too Many Bugs!!! Too many people in common meetings Group 1 Building Blocks Group 2 Origin Too Many Bugs!!! I can never get time with the architects! Group 3 Product Too Many Bugs!!! I have time to help, but don't know how. We pretended to Scrum. Cluster Infrastructure Containers Networking Platform Infrastructure Storage Usability Why does our test automation suck so bad? I don t know what the other teams are working on Developer Experience There are Integration too many Services people on Platform this Management team! User Interface We can t keep up with all the products There are not enough people on this team! Online Productization e2e Product Integration We finished Scale & Performance our goals Internal Tooling All this while working on 6 minor and 4 major releases across the product line.

15 TEAM STRUCTURE circa 16 ATOMIC OPENSHIFT Group 0 Infrastructure Group 1 Kubernetes Group 2 Origin Group 3 Product Container Core Cluster Infra Developer Experience e2e Product Integration Container Security Networking Integration Services Online Continuous Infra Storage Platform Management Productization Platform Infra Storage UXP User Interface Scale & Performance Usability Red Hat Enterprise Atomic Host OpenShift Enterprise OpenShift Online OpenShift Dedicated

16 CASE STUDY #3 Some more bumps... By Maliz Ong CC0 Public Domain

17 TEAM CHARACTERISTICS - Today 21 Hybrid Scrum Teams 3 Week Sprints 6 week 125 releases Engineers RHEL Atomic Host ~6 Month 60+ QE Releases Engineers, OpenShift many Container embedded Platform in teams 20 Documentation Experts 3 Release Engineers 3 Agile Coaches

18 TEAM STRUCTURE Today ATOMIC OPENSHIFT Group 0 Infrastructure Group 1 Kubernetes Group 2 Origin Group 3 Product Group 4 Integration Container Core Cluster Infrastructure Developer Experience Cluster Lifecycle e2e Application Int Container Security Kube Origin Integration Services Continuous Delivery e2e Provider Int Continuous Infra Networking Platform Management Customer Success Scale & Performance Platform Infra Storage User Interface Online Usability Storage UXP

19 WHERE CAN I START?

20 2 weeks Production PO SM Team 5-7 (+/- 2)

21 ANTI-PATTERNS FOR SCALING Never add teams before you really need to. Never optimize before it is time. Never stop inspecting and adapting your process.

22 LEARN TO RECOGNIZE

23 Public Domain

24 THANK YOU plus.google.com/+redhat facebook.com/redhatinc linkedin.com/company/red-hat twitter.com/redhatnews youtube.com/user/redhatvideos

TRAINING AND CERTIFICATION UPDATE

TRAINING AND CERTIFICATION UPDATE Red Hat Enterprise User Group Twin Cities Steve Bonneville Manager, Curriculum Development / Red Hat November 11, 2015 RED HAT LEARNING SUBSCRIPTION One year access to