• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
iAnua storymapping session @ ilean
 

iAnua storymapping session @ ilean

on

  • 333 views

 

Statistics

Views

Total Views
333
Views on SlideShare
233
Embed Views
100

Actions

Likes
1
Downloads
0
Comments
0

4 Embeds 100

http://www.ianua.be 76
http://ianua.be 13
http://www.linkedin.com 9
https://www.linkedin.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Stefaan

iAnua storymapping session @ ilean iAnua storymapping session @ ilean Presentation Transcript

  • Storymapping"The new user story backlog is a map”- Jeff Patton© iAnua ⎜ info@iAnua.be ⎜ @iAnuaBE
  • OUR SERVICESDefine • Capture requirementsDiscover what it needs to do • Identify stakeholders • Gather requirements • Analyze requirements • Document requirements • User researchDesign • User interface designDesign how it needs to work and • Build information architecturelook like • Sketch wireframes • Standardize design patterns • Brief, coach and evaluate visual design and front-end engineering • Prototyping • User testing • Functional analysisManage • Project management (PMI, Prince2)Manage how it is built • In an Agile setting • Agile coaching • Product Ownership • Agile project management Discover more on http://www.ianua.be
  • GREAT PRODUCTS? Customer Business Technology
  • GREAT PRODUCTS? Visually appealing Findable, accessible and usable Reliable and credible Functional, useful and valuableBASED ON: Hierarchy of Needs - Abraham Maslow Designing for Emotion - Aaron Walter Facets of User Experience - Peter Morville
  • GREAT PRODUCTS?SOURCE: The Elements of User Experience, Jesse James Garrett
  • TRADITIONAL BACKLOG
  • USER STORY MAP
  • STORY MAPPINGStory-mapping isa visualizationtechnique toorganize userstories, to showhow the stories fittogether and toprioritize stories.
  • USER STORIES
  • SOURCE: www.comakewith.us, Jeff Patton
  • USER STORIES(User) stories represent functionality that will be valuedby users. * Kent Beck coined theThe 3 C’s: term user stories in Extreme Programming Explained 1st 1. Card: Written description Edition, 1999 2. Conversations about the story 3. Confirmation: tests that convey and document details
  • WHEN
  • SCRUM PROCESS ELABORATED Product Storyroles discovery workshop Opportunity Product backlog backlog PO team Sprint User testing planning meeting Sprint Stakeholder Review Review (demo) Sprint Shippable backlog product Sprint Retro
  • PRODUCT DISCOVERY PROCESS• Story-mapping• Sketching• Prototyping• Competitor review• Analytics• User testing• Expert reviews• Interviews
  • TOGETHER?TEAM
  • (SINGLE) PRODUCT OWNER (MYTH)• As a product owner, you are responsible for delivering a product that is valuable, usable and feasible.• Product team – Product owner / manager – UX expert – Engineering: lead developer / architect – Joined responsibility: building the product backlog together• Facilitator, decision making authority• Potential more rounds of mapping with subject matter experts to richen the map
  • USER STORY MAP Story Maps support the primary intent of user stories: Rich discussion© Jeff Patton, all rights reserved, www.AgileProductDesign.com
  • HOW
  • DEFINE PERSONAS Setting +What do they use thesoftware for Background Wish Familiarity with theMain scenario software / computers
  • BRAINSTORM & MAPPING
  • 2 PARTS: BACKBONE1) Backbone
  • 2 PARTS: AND STORIES (OR TASKS)2) Stories Underneath corresponding backbone item Sorted by priority
  • CARD SORTING time necessity© Jeff Patton, all rights reserved, www.AgileProductDesign.com
  • IDENTIFY PERSONA FOR EACH STORY
  • IDENTIFY PERSONA FOR EACH STORY timenecessity
  • CAN BE USED FOR RELEASE PLANNINGRelease 1Release 2Release 3
  • RELEASE PLANNING time
  • ATTENTION POINTS
  • ATTENTION POINTS• Non functional requirements• Availability of resources• Top-down or bottom-up• Scalability• Makespace (lots of it) ! – Analog or digital?
  • MAKESPACEMAKESPACE Gary Levitt, owner & designer of Mad Mimi
  • ANALOG OR DIGITAL? (OR HYBRID?)
  • ANALOG
  • DIGITAL Level 1 Landing Landing General / Pages - Pages - ZAP Technical Legacy redesign Level 2 technical Registration Login / Online update Coova rebrandings Logged in Set up Migration Login see statistics stories & Login Register (logged in) content Level 3  release PLAT-643 PLAT-645 PLAT-639 PLAT-566 PLAT-567 PLAT-642 session Belfius Set up Zend Online page Q1  sprint 2 Whitelisting 3 Auto-login 5 5 Register 8 2 management update framework (basic) S11 PLAT-644 PLAT-640 32 redirect issues 3 Sum story points C&A update Activate 3 CAP S11 in Sprint PLAT-641 set up demo 32,69 1 environmentFree cap: 0,69 Capacity in sprint6/2 => 20/2 (from team sheet) S12 PLAT-666 PLAT-370 Work out Login snippet Online page ZAP account show assets 33 1 content 1 Log in 5 8 5 3 (Veolia) (total) flow page model CAP S12 PLAT-667 PLAT-371 Change edit content 33,95 phone 2 3 (text+image) numberFree cap: Jira ticket PLAT-668 PLAT-372 Language publish 0,95 3 1 number selection changes21/2 => 6/3 estimate PLAT-373 undo 1 changes S13 Co-existing model Privacy & View & 33 Help page 2 5 2 5 image library 5 (current vs T&Cs update profile new) CAP S13 Asset updates Forgotten zapzone 33,95 5 3 5 existing password page zapzonesFree cap: Speed test 0,95 1 page7/3 => 20/3
  • QUESTIONS & ANSWERS info@iAnua.be @iAnuaBE
  • THANK YOU iAnua info@iAnua.be www.iAnua.be