Download pdf - Evolution Not Revolution. A Case Study of an Enterprise Agile Transformation

EVOLUTION not Revolution

MATT HARASYMCZUK / EVOLUTION NOT REVOLUTION / SEP 18, 2014

MATT HARASYMCZUK

MATTAGILE.com @MATTAGILE #careerconMATTAGILE.com @MATTAGILE #careerconMATTAGILE.com @MATTAGILE

A Case Study of an Enterprise Agile Transformation

MATTAGILE.com @MATTAGILE #careercon

CREATIVITY?!

MATTAGILE.com @MATTAGILE

MATTAGILE.com @MATTAGILE #careerconMATTAGILE.com @MATTAGILE

• Fixed Time • Fixed Price • Fixed Scope

CONSTRAINTS


Phases of GROWTH



PRODUCTIVITY curve



Individuals and interactions over processes and toolsWorking software over comprehensive documentation

Customer collaboration over contract negotiationResponding to change over following a plan

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

Manifesto for AGILE Software Development



AGILE is not a destination AGILE is a direction

Tony Grout, IBM


Organizational CHANGES



The CHOICE of framework



SCRUM, is not a panaceum



EMPIRICAL process



SCRUM, but… daily



Team BUILDING



TRUST and guidance



Anonymous FEEDBACK



Processes NOT people



DIVIDE and conquer - backlog



ACCEPTANCE criteria



LEARNING organization



BALLANCE life - work



Throw yourself in at the DEEP end



COMMUNICATION Framework


MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY

PLANNING2h

DAILY 15m DAILY 15m DAILY 15m DAILY 15m DAILY 15m

REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


PLAN



PLANNING2h


REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


Feedforward NOT Feedback



PLANNING2h


REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


DO



PLANNING2h


REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


PREPARE



PLANNING2h


REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


CHECK



PLANNING2h


REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


SHOW



PLANNING2h


REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


ACT



PLANNING2h


REFINEMENT2h

REVIEW2h

RETROSPECTIVE1h


DEPARTMENT Oriented Organization


Business QA DEV UX Infra

Project A


PROJECT Oriented Structure



Project A

Project B

Project C





Project A

Project B

Project C





Project A

Project B

Project C


PROJECT Oriented Organization



Project A

Project B

Project C


Changes in SOFTWARE DEVELOPMENT



QUALITY does matter



Developer Tools ECOSYSTEM



DEV Practices: TDD, CI, CD



XP: Code Review, Pair Programming



KANBAN: maintenance and bugfixing



Definition of (ALMOST) done



Frequent RELEASES



Spotify engineering CULTURE



BUSINESS VALUES orientation



• Lower "time to market" • Increase "value to market" • Increase "quality to market" • Increase flexibility • Increase visibility • Lower costs • Increase product lifetime

Business VALUES


• Test-driven Development • Evolutionary Design

• Refactoring • CI / CD

• Test-driven Requirements • Functional Tests • BDD

Lower TIME TO MARKET


• Test-driven Requirements • Functional Tests • BDD

Increase VALUE TO MARKET


• Test-driven Development • Test-first and Test-last

• Test-driven Requirements • BDD

• Evolutionary design • Refactoring • Simple Design • CI / CD

Increase QUALITY TO MARKET


• Evolutionary Design • Refactoring • Simple Design • CI / CD

• Test-driven Development • Test-first and Test-last

• Test-driven Requirements

Increase FLEXIBILITY


• Test-driven Requirements • Functional Tests • BDD • CI / CD

Increase VISIBILITY


• Evolutionary design • Simple Design • Refactoring • Collective Code Ownership

• Test-driven Development • Test-last and Test-first • Functional Tests

Lower COST


• Test-Driven Development • Automated Developer Tests

• Evolutionary Design • Refactoring • Simple Design

• Test-driven Requirements • Functional Tests

Increase PRODUCT LIFETIME


Evolution NOT revolution



• Business Values orientation • Building trust and guidance • Scrum, Lean, Kanban as a communication framework • Project oriented organization • Software Development practices • Quality • Evolution not revolution

RECAP

@MATTAGILE

