Download pdf - How Many Wheels You Have to Reinvent

How many wheels you have toREINVENT?!

MATT HARASYMCZUK / RE:invent / OCT 29, 2014

MATT HARASYMCZUK

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

MATTAGILE.com @MATTAGILE #careercon

COMMUNICATION Framework

MATTAGILE.com @MATTAGILE

MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY

PLANNING1h

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

REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h

MATTAGILE.com @MATTAGILE #careerconMATTAGILE.com @MATTAGILE

Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer 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 destinationAGILE is a direction

Tony Grout, IBM


The CHOICE of framework



SCRUM, is not a panaceum



KANBAN: maintenance and bugfixing



Throw yourself in at the DEEP end



PLAN



PLANNING1h


REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h


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

Business VALUES orientation


• 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


Feedforward NOT Feedback



PLANNING1h


REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h


SCRUM, but… daily



TRUST and guidance



DO



PLANNING1h


REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h


Organizational CHANGES



DEPARTMENT Oriented Organization


Business QA DEV SEC 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


PREPARE



PLANNING1h


REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h


DIVIDE and conquer - backlog



ACCEPTANCE criteria



CHECK



PLANNING1h


REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h


Changes in SOFTWARE DEVELOPMENT



QUALITY does matter



Developer Tools ECOSYSTEM



Organizations which design systems are constrained

to produce designs which are copies of the

communication structures of these organizations

Conway’s Law


DEV Practices: TDD, CI, CD



XP: Code Review, Pair Programming



SHOW



PLANNING1h


REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h


Definition of (ALMOST) done



Frequent RELEASES



ACT



PLANNING1h


REFINEMENT2h

REVIEW1h

RETROSPECTIVE1h


LEARNING organization



FEEDFORWARD culture



Processes NOT people



Spotify engineering CULTURE



Evolution NOT revolution



• Scrum, Lean, Kanban as a communication framework• Project oriented organization• Software Development practices• Quality• Evolution not revolution

RECAP

@MATTAGILE

