19
Ten Tonne Skeleton John Shaw Coventry Tech Meetup 12th Jan 2017

Ten Tonne Skeleton

Embed Size (px)

Citation preview

Page 1: Ten Tonne Skeleton

Ten Tonne Skeleton

John Shaw

Coventry Tech Meetup12th Jan 2017

Page 2: Ten Tonne Skeleton

Ten Tonne Skeleton

Start here

Do the backbone next

Add some details

Finish it off

Title inspired by “Ten Tonne Skeleton” by Royal Blood

Page 3: Ten Tonne Skeleton

What the business actually wants

£

Page 4: Ten Tonne Skeleton

Exploring the Problem

Page 5: Ten Tonne Skeleton

Two domains

BusinessProduct OwnerDomain experts

Users

--

Problem focusValue to business

TechnicalArchitect

DevelopersTesters

--

Solution focusWorking software

Page 6: Ten Tonne Skeleton

Balance of value v risk

£Validate the solution

Risk

Establish velocity

Technical debt

Validate the problem

Support the business

Time to market

User experience

Page 7: Ten Tonne Skeleton

Cross-domain problem

BusinessProduct OwnerDomain experts

Users

--

Problem focusValue to business

TechnicalDevelopers

Testers

--

Solution focusWorking software

BA

Tech Lead

Page 8: Ten Tonne Skeleton

Techniques

Page 9: Ten Tonne Skeleton

User Story Mapping

● Backlog management● Epics, themes, stories● Iterative and incremental● Just good enough

Page 10: Ten Tonne Skeleton

Iterative and incremental

This year’s car - iterate

Next year’s car - increment

Page 11: Ten Tonne Skeleton

Story Map

Example story lifecycles:

1. Address tech risk

2. Walking skeleton

3. Flesh it out

4. Added value

Page 12: Ten Tonne Skeleton

Worked Example

Page 13: Ten Tonne Skeleton

1. Address Technical Risk

System A

System B

US-01Interface

GOALMitigate technical risk of interface between systems

Page 14: Ten Tonne Skeleton

2. Walking Skeleton

System A

System B

US-01Interface

Input file

db

US-03Create

US-02Create

User

GOALTestable end-to-end scenario

Page 15: Ten Tonne Skeleton

3. Flesh it Out

System A

System B

US-01Interface

db

US-03Create

US-04Validate

US-05Read UIUS-06

Validate

Input file

US-02Create

User

GOALSupport minimum business need

Page 16: Ten Tonne Skeleton

4. Added Value

System A

System B

US-01Interface

db

US-03Create

US-04Validate

US-05Read UIUS-06

Validate

User

US-07Create UI

US-08Update UI

US-09Delete UI

GOALAdditional business needs

Page 17: Ten Tonne Skeleton

Putting it Together

Page 18: Ten Tonne Skeleton

Balance of value v risk

£● Business dependencies● Time-based risks● Experiments/feedback● Value

● Technical dependencies● Technical risks● Avoid technical debt● Sustainable pace

Ordered backlog

BATech Lead

Enablers

Page 19: Ten Tonne Skeleton

Close

Questions?

John Shaw is a Principal Software Engineer with First Utility.

Twitter: @johnfcshaw

Email: [email protected]

Web: https://www.first-utility.com/Agile in the City Birmingham

@agilecitybham https://twitter.com/agilecitybhamProgramme Board Member