discovery model—an approach for agile at scale

1 © 2015 CA. ALL RIGHTS RESERVED.@CAWORLD #CAWORLD

Discovery Model—An Approach for Agile at Scale

Paulo Barbieri

ADP

Agile Center of Excellence

AMT33S

Agile Management

@therealbarbieri

#CAWorld


For Informational Purposes Only

© 2015 CA. All rights reserved. All trademarks referenced herein belong to their respective companies.

The content provided in this CA World 2015 presentation is intended for informational purposes only and does not form any type of warranty. The information provided by a CA partner and/or CA customer has not been reviewed for accuracy by CA.

Terms of this Presentation


Abstract

When we started our transition to an agile model, many things consultants told us did not make sense. Such as “it is a major culture shift,” “you will need a scaled framework” and “it is easy to learn hard to master.”

During this session you will learn when ADP reached those hurdles and what we are doing to overcome them.

Paulo Barbieri

ADP

Sr Director of Agility Transformation


Agenda

CONTEXT

HOW DID WE KNOW WE NEEDED TO SCALE?

Q&A

THE DISCOVER MODEL

THE DISCOVERY PROCESS

LESSONS LEARNED

1

2

3

4

5

6


Small Business Major Accounts National Accounts Multi National Added Value Services

Comprehensive HRBPO Services

Open ADP-Supported Marketplace

Clients /

> 90,000

Average Client Size

~200 employees

Clients /

> 500,000

Average Client Size

~10 employees

Clients /

> 500

Average Client Size

~4k employees

Clients /

> 1,100

Countries Served

~104

Clients /

> 600,000

Average Client Size

~25

ContextThe ADP Business Organization


Why did we need an agile model?Pain Points that Triggered the Change

Cultural:

Teams not empowered

Different interests within team

Leader directing the work

Lack of accountability

Work Organization:

Too many dependencies

Alignment between strategy and execution

Local optimization costing to the overall process

Technical:

Hard to replicate wins

Economies of scale

Resource availability


Scrum

Team

Small Core TeamDiscovery Team

Executive Sponsor

Scrum Teams are small core teams with a

range of skills sets hacker, hustler, visionary,

average team size of 7, product developer and

designer.

Discovery Team is made up of product leader,

Dev leader, UX researcher and/or architect.

They provide the next “epics” of work for the

Scrum Teams and the product strategy.

Executive Sponsor: The VP IT/Product and

GM ensures teams stay aligned and true to

their vision and strategy. Can assist with tough

decisions or a tie break and removing barriers

across the organization.

Core Team should only require help from the Executive Sponsor ~1 QRT

Stake Holders

Product Discovery Model—Self Organizing and Empowered Teams


Sample of Development Organization with Local Shared Services and CoE Support

Squ

ad

s

L. S

ha

red

Se

rvD

isco

ve

ry T

ea

m

DevOps Arch/Dev PMO

Squad Chief

CoEs

Agility

DevOps

EPM

UX/Design **

Architecture

Testing **

** Every Squad should federate to these CoEs (testing and UX/Design)

Senior Product Owner

Development Leader UX Leader/Architect

t

t

t

t

t

t

t

u

u

u

u

u

u

u

u

u

u

u

u

t

t

t

t

t

t

t

t

t

t

t

t t

t

t

t t t

t

t

t

t

t

t

t

u

u

u

u

u u u

u

u

u

u

u

u

u

u

u


Portfolio Planning Across the Fiscal Year

Yearly Planning of Initiatives (Budgeting)

Roadmap Planning: Continuous Planning on a Cadence

Release Planning: Quarterly Planning of Features

Roadmap Review FY PlanningFY Planning

Q1

Features

Construction Sprints Q2

Features


Features


Features

Construction Sprints

Roadmap Review Roadmap Review


Plan on a cadence. Deliver on demand.

Plan on a Cadence The sprint cycle does not change due to the planning cycle.

Only the content or the goals of the sprints change.

Deploy on Demand

FY16 Qtr 1 FY16 Qtr 2 FY16 Qtr 4FY16 Qtr 3

Minor DeploymentMajor Deployment Major Deployment

J A S O N D J F M A M J

Release

Planning

Release

Planning

Release

Planning

Release

Planning

Milestone


Continuous Planning in One Picture

3 weekSprint

Release PlanningPortfolio Backlog Release Backlog

Dependency Estimation(monthly)

PMO + Discovery Team + Dependent BUs

SCRUM Team+ SPO

Backlog Refinement

StakeholderAlignment(monthly)

ReleaseQuarterly

Discovery Team+ Stakeholders

3 weekSprint

3 weekSprint

SCRUM Team+ SPO

Backlog Refinement

3 weekSprint

Portfolio Planning

Discovery Team

Portfolio Planning

Discovery Team

Portfolio Planning

Discovery Team

Portfolio Planning

Discovery Team


SummaryDiscovery Model Learnings

Key Topics

How to know you need a scaled model?

What is the right model for you?

Where to stop being prescriptive and let the team find the best process?

Findings

The symptoms will be clear when you see them.

SAFe® is a good initial model but not necessarily the end state.

Adopt a model and adjust.

Experiences

Improve predictability to 90 percent and responsiveness to under four days.

Teams and leaders are accountable for outcomes.

Focus next on DevOps.


Q & A


Visual AGILExicon®

Slides in this presentation contain items from the Visual AGILExicon®, which is a trademark of Innolution, LLC and Kenneth S. Rubin.

The Visual AGILExicon is used and described in the book: “Essential Scrum: A Practical Guide to the Most Popular Agile Process.”

You can learn more about the Visual AGILExicon and permitted uses at: http://innolution.com/resources/val-home-page.

Connect with Innolution:

Facebook.com/InnolutionLLC

Twitter.com/krubinagile


For More Information

To learn more, please visit:

http://cainc.to/Nv2VOe

CA World ’15

http://cainc.to/Nv2VOe

http://bit.ly/1wbjjqX

discovery model—an approach for agile at scale

Technology