Slide 1

Slide 1 text

Agile Revisited Dan North @tastapod

Slide 2

Slide 2 text

@tastapod Large projects Functional silos Slow, fragmented technology Process modelled on Civil Engineering 1990s development

Slide 3

Slide 3 text

@tastapod Civil Engineering Cost of errors rises exponentially Assurance through formal hand-offs Plan is intolerant of slippage Hand-offs are detailed and expensive

Slide 4

Slide 4 text

@tastapod Software Engineering Assumes: Cost of errors rises exponentially Assumes: Assurance through formal hand-offs Plan is intolerant of slippage Hand-offs are detailed and expensive

Slide 5

Slide 5 text

@tastapod Agile Then

Slide 6

Slide 6 text

@tastapod The Manifesto Early and continuous delivery of software Welcome changing requirements Deliver frequently Business and developers working together Build projects around motivated individuals Value face-to-face communication Working software is measure of progress Sustainable pace for sponsors, users, team Technical excellence and good design Simplicity Regular reflection and tuning Self-organising teams

Slide 7

Slide 7 text

@tastapod The Brand “Brand(vt): give a product a distinctive identity”

Slide 8

Slide 8 text

@tastapod Early and continuous delivery of software Welcome changing requirements Deliver frequently Business and developers together Build projects around motivated individuals Value face-to-face communication Working software is measure of progress Sustainable pace for sponsors, users, team Technical excellence and good design Simplicity Regular reflection and tuning Self-organising teams Scrum The Brand Agile

Slide 9

Slide 9 text

@tastapod Agile Now http://infoq.com/news/2015/09/agile-bank

Slide 10

Slide 10 text

@tastapod 2010s development Smaller projects Cross-functional “feature teams” Incremental delivery

Slide 11

Slide 11 text

@tastapod 2010s development except… Upstream batching of money Downstream batching of Release

Slide 12

Slide 12 text

@tastapod 2010s development Scrum Water- -fall

Slide 13

Slide 13 text

@tastapod Agile Next

Slide 14

Slide 14 text

@tastapod “Move the people to the work” …but remember they are people! Build your own Light Saber Embrace radical diversity Figure out what a “team” looks like at scale

Slide 15

Slide 15 text

@tastapod Measure Business Impact We can build-ship-measure fast enough Less is more, like surgery Developer “productivity” isn’t a thing Neither is velocity

Slide 16

Slide 16 text

Assume technology is instant* and free* *at least compared to the 1990s Write Build Provision Deploy Monitor

Slide 17

Slide 17 text

@tastapod Embrace Continuous Delivery Two weeks is an illusion, two months doubly so Outcomes create options, requirements emerge Rolling Op-Ex over committed Cap-Ex Investment collaboration over detailed estimation

Slide 18

Slide 18 text

@tastapod Would you use a 1990s computer?

Slide 19

Slide 19 text

@tastapod Then why use a 1990s method?

Slide 20

Slide 20 text

@tastapod The Manifesto Early and continuous delivery of software Welcome changing requirements Deliver frequently Business and developers working together Build projects around motivated individuals Value face-to-face communication Working software is measure of progress Sustainable pace for sponsors, users, team Technical excellence and good design Simplicity Regular reflection and tuning Self-organising teams

Slide 21

Slide 21 text

@tastapod The Manifesto Early and continuous delivery of software value Welcome changing emerging requirements Deliver frequently continually Business and developers and everyone else working together Build projects products around motivated individuals Value face-to-face communication Working software Business impact is measure of progress Sustainable pace for sponsors, users, team all stakeholders Technical excellence and good design Simplicity Regular Continual reflection and tuning Self-organising teams

Slide 22

Slide 22 text

@tastapod Early and continuous delivery of software value Welcome changing emerging requirements Deliver frequently continually Business and developers and everyone else working together Build projects products around motivated individuals Value face-to-face communication Working software Business impact is measure of progress Sustainable pace for sponsors, users, team all stakeholders Technical excellence and good design Simplicity Regular Continual reflection and tuning Self-organising teams Not bad for a first draft!

Slide 23

Slide 23 text

@tastapod Thanks for listening Dan North @tastapod http://dannorth.net