2. Why large • Asking everything to be defined up front
functional • Leads to feature overload
specs • Does not let you evolve, change, reassess
upfront don’t • Hard to follow
work • You end up building more than you need
to
• Still not what the customer really needs
3. • Fast
• Iterative
• A path, not an event
Lean Agile • Just Enough Detail
Requirements • Embrace and adapt to requirements
change
• Remove Duplication
• Tell a Story – Make it easy to follow
• User Point of view
4. User Story 1
High level
description
from user pov
Ideas / Concepts User Story 2
Start with… 1. Idea 1
1:m
High level
description
from user pov
Ideas and their 2. Idea 2
User Story 3
user stories 3. Idea 3
High level
description
Prioritized from user pov
User Story 4
High level
description
from user pov
Used For Project and Sprint Planning
5. User Story 1
UI 1
do only Sketch
High level
description
from user pov
what you need to
Communicate the UI Storyboard
requirements UI 1 UI 2 UI 3 UI 4
Sketch Sketch Sketch Sketch
Mock up
the story Use Case Storyboard
(i.e UI Storyboard with Alternate Flows)
as required UI 1 UI 2 UI 3 UI 4
Sketch Sketch Sketch Sketch
UI 5 UI 6
Sketch Sketch
Delivered as part of a sprint – highly iterative
6. UI 1
Sketch
Build UI Use Case Storyboard
Prototype UI 1 UI 2 UI 3 UI 4
Sketch Sketch Sketch Sketch
Using UI Prototype
built with your
destination UI 5
Sketch
UI 6
Sketch
development platform
tools
Technology (eg. HTML5, Bootstrap.js etc)
Platform
Delivered as part of a sprint – highly iterative
7. Lean Agile
Requirements Ideas / Concepts UI 1
User
with Story 1 Sketch
1. Idea 1 1:m
PowerStory
1:m UI Prototype
Fast 2. Idea 2
built with your
Iterative 3. Idea 3 Use Case Storyboard
development
UI UI UI UI
Just Enough Detail Prioritized platform tools
User
Tell a Story
Story 2 UI UI
Easy to follow
User POV Reused in
A path, not an event real product
Fast iterations
Embrace change refined with feedback
Remove Duplication
Requirements Development
Management and PowerStory tools/stack
Planning tool