50
St Louis Days of .NET 2015

STLDODN 2015 - Scaled Agile Framework (SAFe) in a Nutshell

Embed Size (px)

Citation preview

St Louis Days of .NET 2015

Platinum Sponsors

Silver Sponsors

Gold Sponsors

Polaris Solutions ALM Practice Mgr since Jan ‘12

Been in the software industry since 1999

Runs the Chicago ALM User Group

ALM MVP, PSM, PSD, SPC

Has a *possibly* unhealthy love of Halloween

Polaris Solutions- http://www.polarissolutions.com/

Chicago Visual Studio ALM User Group - http://www.chicagoalmug.org/

Twitter: @OakParkGirl, @ChicagoALM, @TeamPolaris

Blog - http://www.tfswhisperer.com/

There are lots of agile frameworks, I do not know which one is best and I had to start SOMEWHERE? Tell me more!

I already use the SAFe framework, and am interested in hearing another perspective

My team has grown too big and we are struggling with scrum!!

I’ve seen the SAFe diagram and it looks (scary |overwhelming | complex) and I need the crib notes

SAFe seems like a bad idea, but I am open to hearing some alternative ideas about how to apply it

I already hate SAFe and am hoping to heckle you the entire talk

http://www.scaledagileframework.com/continuous-delivery/

PMO, plannin’ and budgeting

projects and initiatives, 12

months at a time

A Scrum team, kickin’ butt and

taking names on their product, 2

weeks at a time

Now let’s assume we have 5, 10, maybe

even 100 active scrum teams!

Scrum Team 1

Scrum Team 2Scrum Team 3

Scrum Team 4

DevOps Team

Scrum Team 1

Scrum Team 2

Scrum Team 3

Scrum Team 4

http://www.scaledagileframework.com/continuous-delivery/

http://w

ww

.scale

dag

ilefr

am

ew

ork

.com

/do

wn

loa

ds/

SAFe is based on nine

immutable, underlying Lean

and Agile principles.

THE

LEVELS

THE

PEOPLE

28

“A system is a network of interdependent components

that work together to try to accomplish the aim of the

system.

A system must have an aim. Without an aim, there is

no system.”

—W. Edwards Deming

THE

BACKLOGS

THE

CADENCE

Deliver on Demand

Major

Release Customer

Upgrade

Customer

Preview

Major

Release New

Feature

Develop on Cadence

PSI PSI PSI PSI PSI

Economic Prioritization

Code Quality

Relentless Improvements

http://w

ww

.scale

dag

ilefr

am

ew

ork

.com

/do

wn

loa

ds/

Take a systems view

Visualize and LIMIT Work in Process (WIP)

Deliver on a cadence but release on demand

Unlock intrinsic motivations

Trust your team!

Most companies I work with who are “going agile” are buried in highly

complex and interdependent legacy apps they cannot just rip and

replace

Most teams I work with don’t have the bandwidth/expertise to also

create, manage, and execute full integration test plans

Most companies are late to the game in bringing agility to DevOps, and

the team/infrastructure/tools in place cannot support an agile release

cadence

Most end users my customers work with don’t actually WANT new

features delivered every 2 weeks

Fear? Uncertainty? Doubt?

Maybe they haven’t ever really looked at SAFe beyond the “Big Picture”

I honestly don’t know. But keep an open mind and check it out.

And in the end, maybe it just really isn’t right for your team…

©2008-2014 Scaled Agile, Inc. and Leffingwell, LLC. All rights reserved.

A proven, publicly-facing framework for applying Lean and Agile practices at enterprise scale

ScaledAgileFramework.com

Synchronizes

alignment,

collaboration and

delivery for large

numbers of teams

CORE VALUES

1. Program Execution

2. Alignment

3. Code Quality

4. Transparency

42

SAFe Guidance: http://www.scaledagileframework.com/guidance/

Principals of Product Development Flow:

http://www.amazon.com/dp/1935401009

Lean Change Management by Jason Little: www.amazon.com/Lean-

Change-Managment-Innovative-Organizational/dp/0990466507/

Platinum Sponsors

Silver Sponsors

Gold Sponsors

Empowered, self-organizing, self-managing cross-functional teams

Operate under program vision, AND architecture & U/X guidance

Valuable, fully-tested software increments every two weeks

47

Working, system-level software at least every two weeks

Aligned to a common mission via a single backlog

Common sprint lengths and estimating

Face-to-face planning cadence

48

Centralized strategy, decentralized execution

Lean budgeting at the Program level

Kanban systems provide portfolio visibility and WIP limits

Objective metrics support governance and kaizen

49

©2008-2014 Scaled Agile, Inc. and Leffingwell, LLC. All rights reserved.

Creator: Scaled

Agile Framework

Agile Enterprise

Coach

To some of the

world’s largest

enterprises

Agile Executive Mentor

BMC, John Deere

Chief Methodologist

Rally Software

Cofounder/Advisor

Ping Identity, Roving

Planet, Silver Creek

Systems, Rally Software

Founder and CEO

ProQuo, Inc., Internet

identity

Senior VP

Rational Software

Responsible for Rational

Unified Process (RUP) &

Promulgation of UML

Founder/CEO

Requisite, Inc.

Makers of RequisitePro

Founder/CEO

RELA, Inc.

Colorado MEDtech