7. Design is making
decisions
• Researching in support of decisions
• Thinking through many potential decisions
• Getting stakeholders to agree on decisions
• Making decisions explicit enough to be built
Wednesday, September 25, 13
9. Not all design work is
represented in Tracker.
Wednesday, September 25, 13
10. How does design
improve velocity?
• Design work unblocks development work.
• Design work should answer questions
about ‘how should this work’ so the
developer doesn’t have to ask them.
• Design work yields assets, so the developer
doesn’t have to make or find them.
Wednesday, September 25, 13
11. Design in the lifecycle
of a story
• Creation
• Definition
• Development
• Acceptance / Rejection
Wednesday, September 25, 13
12. Story creation
• Anyone can create a story
• Design work yields new stories
Wednesday, September 25, 13
13. Story definition
• Design work yields definition for stories
• Responsibility for definition shared
between designer and PM
• Developers can define stories too, but it’s
not a primary responsibility
• Product owner should sign-off each story
definition before developer starts it
Wednesday, September 25, 13
14. Story development
• Development work turns stories into
working software
• In-flight design tune-ups reduce rejections
Rejections have moral, time, overhead cost
Wednesday, September 25, 13
15. Story acceptance
• Rejecting stories based on DEFINED design
is legitimate. (Tune-up to preempt this)
• Any increases in scope due to tune-ups or
rejections should become a new story—no
matter how small!
• Making a designer/PM prioritize a tweak is
sometimes enough to push it off.
Wednesday, September 25, 13
