Why?Lean Agile               What!Requirements               Enabled by PowerStory
Why large       • Asking everything to be defined up frontfunctional      • Leads to feature overloadspecs           • Doe...
• Fast               • Iterative               • A path, not an eventLean Agile     • Just Enough DetailRequirements   • E...
User Story 1                                                High level                                                desc...
User Story 1                                                  UI 1                                   do only       Sketch ...
UI 1                                             SketchBuild UI               Use Case StoryboardPrototype      UI 1      ...
Lean AgileRequirements            Ideas / Concepts                          UI 1                                          ...
Lean AgileRequirements   Build Better               Products
Upcoming SlideShare
Loading in …5
×

Lean agile requirements with power story

3,143 views

Published on

What are Lean Agile Requirements and why you should approach your projects this way.

Published in: Technology, Design
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,143
On SlideShare
0
From Embeds
0
Number of Embeds
2,291
Actions
Shares
0
Downloads
15
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Lean agile requirements with power story

  1. 1. Why?Lean Agile What!Requirements Enabled by PowerStory
  2. 2. Why large • Asking everything to be defined up frontfunctional • Leads to feature overloadspecs • Does not let you evolve, change, reassessupfront don’t • Hard to followwork • You end up building more than you need to • Still not what the customer really needs
  3. 3. • Fast • Iterative • A path, not an eventLean Agile • Just Enough DetailRequirements • Embrace and adapt to requirements change • Remove Duplication • Tell a Story – Make it easy to follow • User Point of view
  4. 4. User Story 1 High level description from user pov Ideas / Concepts User Story 2Start with… 1. Idea 1 1:m High level description from user povIdeas and their 2. Idea 2 User Story 3user 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. 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 SketchMock upthe 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. 6. UI 1 SketchBuild UI Use Case StoryboardPrototype UI 1 UI 2 UI 3 UI 4 Sketch Sketch Sketch SketchUsing UI Prototype built with yourdestination UI 5 Sketch UI 6 Sketch development platform toolsTechnology (eg. HTML5, Bootstrap.js etc)Platform Delivered as part of a sprint – highly iterative
  7. 7. Lean AgileRequirements Ideas / Concepts UI 1 Userwith Story 1 Sketch 1. Idea 1 1:mPowerStory 1:m UI PrototypeFast 2. Idea 2 built with yourIterative 3. Idea 3 Use Case Storyboard development UI UI UI UIJust Enough Detail Prioritized platform tools UserTell a Story Story 2 UI UIEasy to followUser POV Reused inA path, not an event real product Fast iterationsEmbrace change refined with feedbackRemove Duplication Requirements Development Management and PowerStory tools/stack Planning tool
  8. 8. Lean AgileRequirements Build Better Products

×