Download - Failed Agile?

Transcript
Page 1: Failed Agile?

Failed Agile? On agile tech, agile process,

and agile organisationDan Bergh Johnsson

@danbjson dearjunior.blogspot.com

[email protected]

Page 2: Failed Agile?

@danbjson

Manifesto for Agile Software Development

Individuals and interactions over processes and tools Working software over comprehensive documentation

Customer collaboration over contract negotiation Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Page 3: Failed Agile?

http://www.halfarsedagilemanifesto.org

3

Page 4: Failed Agile?

http://programming-motherfucker.com

4

Page 5: Failed Agile?

Agenda

• Hip-hop • Agile technology

• State of the Art • Bang for the Buck • Books

• Agile process • Agile organisation

• … and a travel 5

Page 6: Failed Agile?

Four Elements of Hip-Hop

6

http://www.flickr.com/photos/coupdoreille/11980711276/ http://www.flickr.com/photos/93163771@N08/11980682486/ http://www.flickr.com/photos/49180634@N05/10678483545 http://www.flickr.com/photos/54237011@N02/5032121885/

Page 7: Failed Agile?

Three Elements of Agile

7

Organisation

Process

Technology

http://www.flickr.com/photos/82397118@N00/5173687358 http://www.flickr.com/photos/85546319@N04/9546047237 http://www.flickr.com/photos/85546319@N04/11874970786

Page 8: Failed Agile?

Three Maslow-pyramids for Agile

8

Avant-garde

Well-known

Established

https://www.flickr.com/photos/s_w_ellis/3859525046/

Page 9: Failed Agile?

@danbjson

The Manifest, again

Individuals and interactions over processes and tools Working software over comprehensive documentation

Customer collaboration over contract negotiation Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Page 10: Failed Agile?

10

Organisation

Process

TechnologyWe build systems that rock!

Page 11: Failed Agile?

Technology

11

unit testsbuild server

domain-based code (DDD)automated acceptance tests

platform as code- vagrant, puppet TDD

context-based test/ exploratory testing

daily releaseversioned databases

feature toggletwo generation architecture

build pipeline

system quality testing

Page 12: Failed Agile?

Bang for the BuckAgile Testing

• Human testning á la Exploratory Testing in sprint • A few automated acceptance tests

Controlled Technical Debt • Quality reports e g Sonar • Automated acceptance tests • Daily release - eventually

A database in each mans pot • Automated rigging of test data • Automated rigging of structure - versioned DB • (spice with) Vagrant/Puppet, or bash-script

12

Page 13: Failed Agile?

Books

Implementing Domain Driven Design [Vernon]

Refactoring Databases [Ambler/Sadalage]

97 Things Every Programmer Should Know [antologi]

Continuous Delivery [Humble/Farley]

https://www.flickr.com/photos/shutterhacks/4474421855

Page 14: Failed Agile?

14

Organisation

Teknik

Process

We ensure things get done without waste or detours!

Page 15: Failed Agile?

Process

15

test in team / test in sprint

sprint retrospective

forecast-based planning

MVP-releasedomain modelling a la DDD

hypothesis-driven, A/B-testning

project retrospectiveeffect-governed project

demo

non-functional requirements

sprint 1-2 wkanban

Specification by Example

Page 16: Failed Agile?

Bang for the Buck

16

lojalty relevancescale PV/UV (w) #shares

rod GA Tw+FBnow/base 20 1000ROI 25 1000ambition 50 5000

project retrospective

1/3-release; MVP

Page 17: Failed Agile?

Books

Succeeding with Agile [Cohn]

Lean Software Development [Poppendieck]

Domain Driven Design [Evans]

Specification by Example [Adzic]

Impact Mapping [Adzic] Agile Estimation and

Planning [Cohn]

https://www.flickr.com/photos/shutterhacks/4474421855

Page 18: Failed Agile?

18

Process

Technology

Organisation

We create an organisation where people work by inner drive, and direct that drive toward a purpose!

Page 19: Failed Agile?

Organisation

19

self-organised team

portfolio management

destilled processes and standards

sociocracy Beyond Budgeting

”Ambition to Action”

flexible work-hours

multi-team coordination

open salarieslattice-

organisations

Page 20: Failed Agile?

Bang for the Buck

?20

Page 21: Failed Agile?

@danbjson

Frederick Winslow Taylor

(1856 - 1915)([1904]1911 – still going

strong)

Page 22: Failed Agile?

@danbjson

Drive á la Daniel Pink

Autonomy

MasteryPurpose

Page 23: Failed Agile?

@danbjson

ἐκκλησία - responsible autonomi

http://www.flickr.com/photos/robwallace/6950767/

Page 24: Failed Agile?

@danbjson

Process office of SVTi

Page 25: Failed Agile?

@danbjson

SVTi: ecclesia + double loop learning

Page 26: Failed Agile?

Bang for the Buck

Central targets - Specific, measurable, possible to monitor - Interpreted locally by each team

Management meeting agenda - What can we do specifically right now to support ”autonomy, mastery, purpose”?

26

Page 27: Failed Agile?

Books

LESS! Essays on Business Transformations [antologi]

Principles of Scientific Management [Taylor]

The Human Side of Enterprise [McGregor]

Drive [Pink] Implementing Beyond

Budgeting [Bogsnes] Radical Management

[Denning]

Page 28: Failed Agile?

@danbjson

Take-away

Three elements in balance: Technology, Process,

Organisation Not making progress in one element

might depend on state of another element

Page 29: Failed Agile?

</Failed Agile?>

Dan Bergh Johnsson @danbjson

dearjunior.blogspot.com [email protected]