30
How to build bad software

Agile crash course - how to build bad software

Embed Size (px)

Citation preview

How to build bad software

The problem

Strong

LightCheap

The problem

Strong

Light

Cheap

The problem

Strong

Light

Cheap

The problem

Strong

Light

Cheap

The problem

Strong

LightCheap

The problem

Scope

QualityTime/cost

The solution according to waterfall...

“Functional Requirements Document”

“Schedule of work”

The solution according to waterfall...

What if you could fix time, cost AND quality?

The agile manifesto

The agile manifesto

As a... I want a... So I can

The ‘user story’

Member of the library An online accountChange how long I have

borrowed a book for without going back into the library

User Feature Benefit

Backlog of stories1 2 3

5 8 13

21

Sprint

In o

rder

of i

ncre

asin

g p

rior

ity

Sprint board

Pulled from backlog into

sprint

Who is working on it?

Stan (for the moment)

UAT (User Acceptance

Testing)

Fixed?

DoD(Definition of done)

No Yes

Burndown chart

Sprint retrospective

The agile manifesto

“I spent 15 years breeding faster horses”

“focus is the art of saying no”

MVP

The agile manifesto

The problem with FRDs and SoWs

Iterative development

The agile manifesto

User-centric design

Lean

“the aggregation of marginal gains”

The new “HOT PANTS” by Team GB...

Iterative development

● Fix time, cost and quality and compromise on none● Transparent communication in the team● Get to market quickly● Respond to a changing market

“Arrive at the ‘final’ product in predictable, incremental steps & build the right thing for the right audience”

What’s the point of Agile anyway?