Embed Size (px)
Citation preview
The plan
the IT team meet
regularly
liaise with the
stakeholder
self organise
share the vision
of the product
(mostly)
represent the
consultant
assess technical
debt
separate work
into tasks
define “done”perform code
reviews
Test
set up backlogsrefine
acceptance
criteria
celebrate
product releaseslimit strategic
changes
write (enough)
user stories
think in terms of
product
increments
unit test
have an
impediment
bulldozer(!)
BACKLOGIN PROGRESS
DONE
the IT team meet
regularly
liaise with the
stakeholder
self organise
share the vision
of the product
(mostly)
represent the
consultant
assess technical
debt
separate work
into tasks
define “done”perform code
reviews
Test
set up backlogsrefine
acceptance
criteria
celebrate
product releaseslimit strategic
changes
write (enough)
user stories
think in terms of
product
increments
unit test
have an
impediment
bulldozer(!)
BACKLOGIN PROGRESS
DONE
The book
The problem
with the plan
The next plan
The introduction
The joy of arts and crafts(!)
The board
The stand-up
The avatar
The challenges
The 12 steps
Step one: admit you have a problem
Step two: recognise a higher power
Step three: examine past errors
DONE
Step five: learn to live with a new code of behaviour
Step six: skip to step twelve
Step twelve: help others
Thank you!Peter MooreLook at your Datawww.lookatyourdata.co.uk www.lookatyourdata.co.uktwitter.com/factgasm (@factgasm)
