The Agile TheaterStarring Scrum, The Scrum Master,

Product Owner, Agile Team, The Sprint.Guest Appearance – The Waterfall

1

Achieving Real Agility in the Digital Age• The Agile Theater – What is

it, Why is it happening• Real/Modern Agility• Concrete Examples of

Theater vs Modern/Real Agility behavior

• What can you do next

2

Yuval Yeret

About Me• Help people spark Real business agility at scale.

• Allergic to Agile Theater (And Dust, and probably Dog/Cat hair)

• Senior enterprise agility coach at AgileSparks, an international lean agile consulting company with offices in Boston, Israel, India.

• Blogging at yuvalyeret.com.

• Living in Newton, MA – heading business development and agile consulting engagements for AgileSparks in the US.

• Email me questions/feedback/suggestions at yuval@agilesparks.com or 857-218-9585.

• Slides already available at https://www.linkedin.com/in/yuvalyeret.

3

Agile Team2

Agile Team1

Ongoing

DoneFeatures

Backlog

Develop

Feature/

Sprint

in

Progress

Story-level

Test & Fix

Deploy

ment

Done Ongoing Done

Stories

Backlog

Ongoing

Specify

Done

H.6

H.0

H.1H.2

H.3

H.4H.5D2

D3

T2

T1

D1

P

1

H.7

T2

Implement Feature by Stories

How does an agile project/program looks like?

(by the book…)

Agile Team2

Agile Team1

Ongoing

DoneFeatures

Backlog

Develop

Feature/

Sprint

in

Progress

Story-level

Test & Fix

Deploym

ent

Done Ongoing Done

Stories

Backlog

End of

Release

Testing

Ongoing DoneOngoing

Specify

Done

H.6

H.0

H.1H.2

H.3

H.4H.5D2

D3

T2

T1

D1

P1

H.7

T2

Implement Feature by Stories

UAT

Regression

Performance

Security

Functional

Progression

Exploratory

ATDD

Au

to

Long wait for the

endgame

Real Life… Not so agile...

a.k.a WaterScrumFall

“Sprint is too short for everything we need to

achieve DONE”

“Let’s leave the serious testing for the release

testing phase”

Platform

Matrix

Real

Network

Ongoing

To Do Agile Development

& Testing

AutomatedDelivery

AutoDeployment

Done Ongoing DoneOngoing

AgilePlanning

Done Ongoing Done

Real Business Agility

Frequent Feature Delivery

Continuous Integration

Predictable, Repeatable, Non-Event

Production

Ongoing

Production / Done

Roadmap AgileDevelopment

& Testing

ReleaseActivities

Done Ongoing DoneOngoing

ReleaseBacklog / Product

Requirements

Done

Ongoing

Deployment

Done

“Reasonable” Agile Development

V1V2V3

Continuous Integration

Agile Theater Approach to Teams

Henrik Kniberg

Client team

C C C

Test team

T T T

DB team

D D D

Server team

S S S

Feature team 1

CC

S

D

TT

C

S

D

T

Feature team 2

D

S

DB

Server

Client

User

Communitiesof interest

Agile Theater – “Empowered Teams and Individuals”

Agile Theater – “Sprint/Release Planning”

http://www.youtube.com/watch?v=FGfplQ1FUFs

Why?

See Kent Beck’s idea as described by Markus Gartner at http://www.shino.de/2010/11/04/software-g-forces-the-effects-of-acceleration/

13

The Law of

Raspberry Jam: the

wider any culture is

spread, the thinner

it gets.

Alvin Toffler

http://www.agilesparks.com/AS%20Way

So how can we close the curtain on the Agile Theater and start to establish

Real Business Agility? 15

House of Lean

LEADERSHIP

Resp

ect

for

people

an

d c

ulture

Flo

w

Innovation

Rele

ntless

impro

vem

ent

VALUE

Agile Team2

Agile Team1

Ongoing

DoneFeatures

Backlog

Develop

Feature/

Sprint

in

Progress

Story-level

Test & Fix

Deploym

ent

Done Ongoing Done

Stories

Backlog

End of

Release

Testing

Ongoing DoneOngoing

Specify

Done

H.6

H.0

H.1H.2

H.3

H.4H.5D2

D3

T2

T1

D1

P1

H.7

T2

Implement Feature by Stories

UAT

Regression

Performance

Security

Functional

Progression

Exploratory

ATDD

Au

to

Long wait for the

endgame

Real Life… Not so agile...

a.k.a WaterScrumFall

“Sprint is too short for everything we need to

achieve DONE”

“Let’s leave the serious testing for the release

testing phase”

Platform

Matrix

Real

Network

Imp

rovem

en

t

TraditionalProcesses

Agile w/o Eng Practices/CI

Reduce Batch Size FurtherWITH

Great automation and leaner processes

The result - only a limited amount

of feedback is early and effective

0

20

40

60

80

100

120

1 3 5 7 9 11 13 15 17 19 21 23

done

done done

40% 60%

Identify coverage that happens outside the sprint. Which is the biggest quality risk if found late?

Agile Team2

Agile Team1

Ongoing

DoneFeatures

Backlog

Develop

Feature/

Sprint

in

Progress

Story-level

Test & Fix

Deploym

ent

Done Ongoing Done

Stories

Backlog

Ready

For

Feature

Test

Test

Feature-

level

Ongoing Done

End of

Release

Testing

Ongoing DoneOngoing

Specify

Done

T

T

TH.6

H.0

H.1H.2

H.3

H.4H.5D2

D3

T2

T1

D1P1

H.7

T2

Implement Feature by Stories

UAT

Regression

Performance

Security

Functional

Progression

Exploratory

Try - Slowly shifting left towards Continuous

Quality and adding the Feature-level testing

stage in the pipeline

Add Feature/Epic level testing

1. Add Feature/Epic/Iteration level

testing.

2. left-shift more and more testing through automation, enabling teams using

environments/tools/knowhow and more.

• Most expensive automation to develop, run & maintain, so minimize!!!

• Move majority of E2E testing coverage to Service/API layer

• QTP/UFT/Selenium/PerfectoMobile/etc.

UI

• “The Workhorse” of enterprise agile testing

• Created by testers & developers on agile teams supported by frameworks/guidance by Automation CoE

• soapUI, etc.

Acceptance (Service/API)

• Leverage Agile Teams developer testing to reduce coverage needs

• Ability to automatically detect (through coverage tools etc.) what is covered

Unit Testing

Manual

http://www.mountaingoatsoftware.com/blog/the-forgotten-layer-of-the-test-automation-pyramid

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

23

Teams manage

iterations using

Stories Board

Programs manage feature E2E Flow (all

the way to OPS) using Features Board

Business Units/Portfolios manage

Epics/Initiatives using Portfolio Boards

Implement Lean/Agile Principles/Practices beyond the team

Expand one level

Agile Theater Approach to Teams

Henrik Kniberg

Client team

C C C

Test team

T T T

DB team

D D D

Server team

S S S

Feature team 1

CC

S

D

TT

C

S

D

T

Feature team 2

D

S

DB

Server

Client

User

Communitiesof interest

If it’s too much to create “Feature Teams” at least create “Feature Trains”

Business Product Mgmt

Hardware Software Testing

A G I L E R E L E A S E T R A I N

Agile Teams

PMO DeploymentSys Eng.

27

Credit - Udi Weinberg – HP Software

Best Practice – Agile Testers DRIVE quality

ATDD = Acceptance Test Driven Development -Build Quality Into Design – preventing defects

rather than just finding them

Elaborate Requirements

Test DesignTechnical

DesignCoding / Unit

TestingTest Execution

+ FixingDone

1. ATDD ThinkingUse test scenarios to guidedesign (which can then happen using TDD, or not…)

http://www.agilesparks.com/test-first-reading-list

Test Automation

The Agile TheaterStarring Scrum, The Scrum Master,

Product Owner, Agile Team, The Sprint.Guest Appearance – The Waterfall

30

Achieving Real Agility in the Digital Age• The Agile Theater – What is

it, Why is it happening• Real/Modern Agility• Concrete Examples of

Theater vs Modern/Real Agility behavior

• What can you do next

31

Yuval Yeret

http://bit.ly/safectperfecto

Use

PM2020%

discount until 4/16

33

http://bit.ly/scaledagiletestingboston

Use

PM2020%

discount until 4/21

Questions?• Email me questions/feedback/suggestions at

yuval@agilesparks.com or 857-218-9585.

• Slides already available at https://www.linkedin.com/in/yuvalyeret.

• Would love to help you move beyond the Agile Theater in your context.