Goal-Directed Design: Scenarios User Stories Setting the Vision - PowerPoint PPT Presentation

Introduction Goal-Directed Design: Scenarios User Stories Setting the Vision Scenarios Scenario- Based Design Jörg Cassens Tutorial References SoSe 2019 Contextual Design of Interactive Systems SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 1 / 80

Introduction User Stories Scenarios Scenario- Based Design Introduction Tutorial References SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 2 / 80

Assignment 6.1: Go & Carroll Required Reading Introduction User Stories Required reading for week 3 Scenarios Go, Kentaro, and John M. Carroll. “The blind men and the elephant: Views of Scenario- Based scenario-based system design.” interactions 11, no. 6 (2004): 44-53. Design Tutorial The texts will be discussed in the tutorial 14.05.2019 References Course readings can be downloaded in the learnweb Every text has a wiki-page in the learnweb Use it to describe the text Use it to link the text to the course Results of the discussion may also be written up SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 3 / 80

Where are we? Introduction Last time: We learned to create personas User Stories We will now use these personas to generate two design models Scenarios User stories Scenario- Based Scenarios Design User stories: Tutorial References Describe functionality that will be valuable to user of sofware. A feature request from a user’s point of view. It is NOT a bug report or a functional specification. It is NOT a technical design document. Scenarios: Stories or scenarios as a means of imagining ideal user interactions Using those scenarios to extract design requirements SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 4 / 80

Narrative Narrative, or storytelling, one of the oldest human activities Introduction Power of narrative known to communicate ideas User Stories Scenarios However, narrative is also one of our most powerful creative methods Scenario- From a very young age, we are accustomed to using stories to think about Based Design possibilities, and this is an effective way to imagine a new and better future for Tutorial our users References Imagining a story about a person using our product leverages our creativity to a greater power than when we just imagine a better form factor or configuration of screen elements Because of the intrinsically social aspect of narrative, it is an effective and compelling way to share good ideas among team members and stakeholder Experiences designed around a narrative tend to be more comprehensible and engaging for users because they are structured around a story SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 5 / 80

Narration of Interaction Introduction User Stories Scenarios Narrative also lends itself to effective visual depictions of interactive products Scenario- Based Design Interaction design is first and foremost the design of behaviour that occurs over Tutorial time References Therefore, a narrative structure combined with the support of fast and flexible visualization tools (such as a whiteboard) is perfectly suited for motivating, envisioning, representing, and validating interaction concepts SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 6 / 80

Narration as Design Tool Introduction User Stories Scenarios Scenario- Based Design Tutorial References Dell (2018) SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 7 / 80

Introduction User Stories Writing Stories Scenarios Scenario- Based User Stories Design Tutorial References SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 8 / 80

User Stories as a Design Tool Introduction User Stories Shifs the focus from the product to what the eventual owner / user needs or Writing Stories wants it to do. Scenarios Scenario- A customer buys your product to help them do something. Based Design Your stories must help them do it. Tutorial A user has to do something using your product. References Your stories must help them do it. Remember our focus is on the goal, not the means The narrative should capture what the owner / customer wants to achieve and map that to specific activities SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 9 / 80

Components Components Introduction As a [role], User Stories Writing Stories I can [functionality] Scenarios so that [rationale] Scenario- Based Design Role Tutorial Persona; References important and specific class of user Functionality Activity, action, task Rationale Reason, motivation The rationale demonstrates the value to the eventual user / owner and determines its priority and the effort to be expended. SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 10 / 80

Example Introduction User Stories Example Writing Stories Scenarios As a music fan, Scenario- Based I can establish an account, Design so that I can legally stream and download music. Tutorial References Role is important to the eventual owner Rationale demonstrates value to the eventual owner Functionality enables the value to be achieved SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 11 / 80

Scope Introduction Too broad = impossible to test/code User Stories Too narrow = more time spent specifying than implementing Writing Stories Scenarios Split long stories (“epics”) into smaller pieces Scenario- Rather than specify small details, get those in conversations with customer & Based Design annotate story Tutorial Big stories can serve as placeholders for areas of the system that still need to be References discussed Example “As an administrator I can manage posts to the site so that I can control the content our customers see” SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 12 / 80

Scope Introduction Too broad = impossible to test/code User Stories Too narrow = more time spent specifying than implementing Writing Stories Scenarios Split long stories (“epics”) into smaller pieces Scenario- Rather than specify small details, get those in conversations with customer & Based Design annotate story Tutorial Big stories can serve as placeholders for areas of the system that still need to be References discussed manage? Example what content? “As an administrator I can manage control? posts to the site so that I can control the content our customers see” Split epics into smaller stories SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 12 / 80

Introduction User Stories Writing Stories Scenarios Scenario- Writing Stories Based Design Tutorial References SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 13 / 80

Writing Stories Introduction User-centred stories User Stories In agile approaches, ofen relegated to customer Writing Stories Scenarios Written in language of business to allow prioritization Customer is primary product visionary Scenario- Based Design Writing good stories needs practice & insight Tutorial Customer are ofen not the right stakeholder to write the stories References Good stories can INVEST Independent Negotiable Valuable to users or customers Estimable Small Testable SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 14 / 80

Independent & Negotiable Introduction User Stories Writing Stories Independent Scenarios Each story has it’s own value Scenario- Don’t make stories depend on other stories Based Design Stories that depend on other stories are difficult to prioritize and estimate Tutorial Negotiable References Stories serve as reminders not contracts Details need to be fleshed out in conversation Stories should have a phrase or sentence to serve as reminder to have conversation & notes about conversation SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 15 / 80

Valuable & Estimable Introduction Valuable User Stories Writing Stories Both to people using the sofware and paying for the sofware Scenarios Avoid stories valued only by developers (make the benefits to customers/users Scenario- apparent for these stories) Based Design Estimable Tutorial We must have enough information that we can properly size a story so that we References plan properly and commit to our work. Reasons why story might not be estimable: Designers lack domain knowledge Get details from customer Story is too big Split the story into smaller ones SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 16 / 80

Small & Testable Introduction Small User Stories Writing Stories User Stories should be small enough that they are able to be completed within a Scenarios sprint. Scenario- (e.g., A few hours to a few days of design/ development time.) Based Design Makes them easy to use in planning Tutorial Split compound & complex stories References Combine too small stories Testable All members of the team need a clear and precise way to verify whether or not a User Story has been completed. Can’t tell if story is done without tests Tests can be automatable or not SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 17 / 80

Example Introduction User Stories Example Writing Stories Scenarios as a bank customer i can check my Scenario- account online so that i can see my Based Design balance 24/7 Tutorial References SoSe 2019 Jörg Cassens – Goal-Directed Design: Scenarios 18 / 80