2. Clear, visible process
across the company
Measurable value from
development
Lightweight, easily
adaptable to future
change.
Friday, 26 October 12
3. Bugs
Ideas Planning Development Measure
Roadmap
Friday, 26 October 12
4. Bugs Bugs
Defects in the product as reported by customers or staff, or issues
raised by any error logging tools.
Ideas
Ideas Planning Development
Suggestions for the product come from inside the company, or from
external sources, like customer service channels, or any external
forums for discussion of the product.
Roadmap Roadmap
Company strategy, defined in terms of high level requirements, or
high level themes for user stories.
Friday, 26 October 12
5. Planning
Bugs
Input from each board has a qualifying
process before it makes it to planning.
Bugs are confirmed as reproducible,
Ideas are described in enough detail to be
Ideas Planning Development
understood by a product manager
Items on the roadmap are confirmed as still
relevant to the company strategy.
Requirements or draft stories are fleshed
out here, with sketches or wireframes, until
they are in a state that can be estimated
Roadmap upon by a development team, and
delivered.
Friday, 26 October 12
6. Planning
Bugs
Developer Estimation
Review Meeting
Ideas Planning Development
Roadmap
Friday, 26 October 12
7. Planning
Bugs
Developer Estimation
Review Meeting
Ideas Planning Development
One developer and the product
manager reviews any story or
requirement that needs an
estimate in this meeting.
Roadmap Together they weed out technical
issues, and dependencies before
a group estimation, or identify
areas that need further definition
before estimation is possible.
Friday, 26 October 12
8. Planning
Bugs
Developer Estimation
Review Meeting
Ideas Planning Development
In an estimation meeting the
developers, and the product
manager run through the stories
and allocate a points value to
Roadmap each story based on perceived
difficulty across the whole team.
Friday, 26 October 12
9. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
Roadmap
Friday, 26 October 12
10. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
Stories and requirements are assigned to a sprint
in a sprint planning meeting.
A product manager reviews the stories going into
the sprint with the development team, and the
Roadmap
development team commit to delivering the work,
based on the velocity agreed in the last sprint
retrospective.
Friday, 26 October 12
11. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
Every morning, the development team and the
product manager runs a 15 min stand-up meeting,
answering the following questions:
- What you did yesterday?
Roadmap doing today?
- What are
- What is blocking you?
Sprint progress is reviewed, against what was
committed to for the sprint.
Friday, 26 October 12
12. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
On the last day of the sprint, the team members
run through the work they’ve completed to the
rest of the team, and the product manager.
Original ‘owners’ of an idea are optionally
Roadmap to see the requested story delivered.
present,
Friday, 26 October 12
13. Sprint planning and
development
Bugs
Sprint Daily Sprint Retro-
planning Standup Demo spective
Ideas Planning Development
After the sprint demo, comes the retrospective.
The team discusses the good and bad aspects
of the sprint, and any changes to their process
they’d like see internally.
The team commit to a velocity for the next
Roadmap
sprint, based on the points delivered, to help
plan the next sprint.
Friday, 26 October 12
14. Bugs
Ideas Planning Development
Roadmap
Friday, 26 October 12
16. Bugs
Ideas Planning Development
Roadmap
Filing bugs
Friday, 26 October 12
17. Reviewed &
Inbox Accepted
needs input
Bugs
Bug with
description
Ideas Planning Development
Roadmap
Friday, 26 October 12
18. Reviewed &
Inbox Accepted
needs input
Bugs Bug with
description, and
steps to
reproduce, etc.
Ideas Planning Development
Roadmap
Friday, 26 October 12
19. Reviewed &
Inbox Accepted
needs input
Bugs Bug with
description, and
steps to
reproduce, etc.
Ideas Planning Development
Roadmap
Friday, 26 October 12
20. Bugs
Ideas Planning Development
Roadmap
Collecting Ideas
Friday, 26 October 12
21. Awaiting Review Under review Accepted
Bugs
Idea from inside
the company
Ideas Planning
External customer Development
request
Roadmap
Ideas come from any where inside, and
outside the company
Friday, 26 October 12
22. Awaiting Review Under review Accepted
Bugs
Idea from inside
the company
Ideas Planning
External customer Development
request
Roadmap
A product manager works with the originator,
to flesh them out.
Friday, 26 October 12
23. Awaiting Review Under review Accepted
Bugs
Idea from inside
the company
Ideas Planning
External customer Development
request
Roadmap
When it’s understood, it can be moved to the
planning board
Friday, 26 October 12
24. Bugs
Ideas Planning Development
Roadmap
How the roadmap
drives product
Friday, 26 October 12
25. Now
To avoid waste,
user stories and
features only
become more
detailed and
granular as they
get closer to
development.
Future
Friday, 26 October 12
26. Q3 Q4 2013
Bugs
Update sign-in Public sign-in for Scope 3
process companies calculation
Ideas Defined and Planning Development
documented API CRC Reporting
RAG status on
Roadmap suppliers
The Roadmap gives a high level view of areas
of focus in coming months.
Friday, 26 October 12
27. Q3 Q4 2013
Bugs
Update sign-in Public sign-in for Scope 3
process companies calculation
Ideas Defined and Planning Development
documented API CRC Reporting
RAG status on
Roadmap suppliers
New cards are created based on these
themes in planning
Friday, 26 October 12
28. Bugs
Ideas Planning Development
Roadmap
Defining deliverable
work
Friday, 26 October 12
29. Ready for
To Do Spec and dev review UX and Design
Estimation
User story
Planning Development
The aim is to get cards from the left, to the right.
Friday, 26 October 12
30. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
It’s okay for cards to be sent back and forth
between stages if they need further clarification
Friday, 26 October 12
31. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
It’s okay for cards to be sent back and forth
between stages if they need further clarification
Friday, 26 October 12
32. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
It’s okay for cards to be sent back and forth
between stages if they need further clarification
Friday, 26 October 12
33. Ready for
To Do Spec and dev review UX and Design
Estimation
User story User story
Planning Development
Cards are ready when they fit the format for a
product, are well understood and have clear
measurement criteria
Friday, 26 October 12
34. Main goals for dev process
Simplicity
Transparency
Flexibility
Friday, 26 October 12
35. Bugs
Ideas Planning Development
Roadmap
Delivering the work
Friday, 26 October 12
36. Estimated Current sprint In Progress Pull Request QA Complete
A user story
A second
story
A user story
A second
story
Prioritising estimated stories
Friday, 26 October 12
37. Estimated Current sprint In Progress Pull Request QA Complete
A user story A user story
A second A second
story story
Building a sprint, based on
Friday, 26 October 12
velocity
38. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
Picking up work from the
Friday, 26 October 12
current sprint backlog
39. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
Code review from other
Friday, 26 October 12
developer in pull request
40. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
QA performed by product
Friday, 26 October 12
owner
41. Estimated Current sprint In Progress Pull Request QA Complete
A second A user story
A user story
story
A second
story
Feature ready for release
Friday, 26 October 12
42. Completed features by this point
should be in a state to be
Complete 0.17.1 0.17.2
deployed to production.
A user story A user story Bug fix
Depending on the business
need, they can be pushed
directly to production (in the
A another
story User story case of severe bugs etc), or as
specific releases.
The aspiration here is to working,
QA’d, and CR’d code
automatically pushed to
production, where features can
be rolled out gradually, or
switched on or off independently
of code releases.
Deployment
Friday, 26 October 12
43. Bugs
Ideas Planning Development Measure
Roadmap
Friday, 26 October 12
44. Measuring the value of features
Bugs
Development doesn’t end at deployment.
Ideas every feature needs accompanying metrics, but
Not Planning Development Measure
most should have them.
Did a feature have the expected result?
Roadmap can we tell?
How
Are we measuring the right data here?
How might we improve the feature?
How are we getting feedback?
Friday, 26 October 12
45. Measuring the value of features
Bugs
Quantitive Qualitative
Ideas Planning In-app chat
Development Measure
Kissmetrics (eg. Olark)
(individual user
interactions)
Support software
(desk.com)
Google Analytics
Roadmap trends, and
(larger
heatmaps) User testing
(recording how features
are used in beta / testing)
Ad-hoc API/DB
Queries
Problem &
solution interviews
( showing prototypes to
users before building)
Friday, 26 October 12
