Writing Valuable Requirements: From Personas to Use Cases and User Stories

Transcription

1 Writing Valuable Requirements: From Personas to Use Cases and User Stories Mattias Arvola SICS East Swedish ICT Department of Computer and Information Science

2

3 3 Value in Use The value of a product, system or service does not exist until it is being used Values that stakeholders have that guide prioritisation and selection Value in use is the outcomes achieved by stakeholders in collaboration in a process Value in use are the qualities and experiences of stakeholders in the usage process

4 4 Value Propositions Value is defined by the stakeholder (e.g. users) Value is co-created by the stakeholders It is only the customer (or user in design-speak) who can say if what was done for her provided the desired outcome(s) You can only offer value propositions = the value we believe we can provide for the customer

5 5 Value in Use for Your Project Who are the most central people in co-creating the intended value? How can you get to understand the value-in-use for them? What is the role of your software? What could be a relevant value proposition for the user? Beyond software, what would need to be in place for the value-in-use to be achieved?

6 Maria, Tom and Owen start the Minnesmark app to go on a computer augmented treasure hunt. Maria chooses which treasure hunt and they are off. They take part of stories at places along the way. Minnesmark Marker-based augmented reality is used to animate the story so that virtual objects are embedded with the camera view in the background. There are, at some places, panoramas that show the place as it once was. Tom navigate a panorama by holding his ipad infront of him while turning around. They find treasures in the form of various media along the way, and the treasures are sent to Owen's address at the end of the treasure hunt. It's great that Owen's teacher could use the Minnesmark Editor to set up this trail for them.

7 Requirements Is About Communication 7

8 Customer personas Brainstorming Stakeholders External influences (competitors, media, regulatory agencies) Goals Ideas Brand Business objectives Constraints Differentiation Feature parity Regulations Persona goals User personas Scenarios Mental models Goals Environments Skills Requirements (data needs, functional needs, qualities, constraints, experience attributes)

9 Different Kinds of Requirements 9 Data Objects (nouns) + attributes from a persona s mental model Things that someone search for, manipulate, read Functions The verbs that describe what users should be able to do with the product (or the data) Product Qualities Performance, response time, security Constraints External factors, i.e. deadline, cost, law UX goals/attributes What users should experience (adjectives/adverbs)

10 10 SOURCE DATA FUNCTION QUALITY CONSTRAINT PERSONA Scenario Mental model Goals Context Skills STAKEHOLDER COMPETITION Number of photos left Be able to remove photos Understand the effect of settings Handle sharp contrast automatically >6 megapixel Professional look & feel Visible screen in sun light Fit the hand of average female Price kr

11 11 Brainstorming Create context scenarios Generate potential requirements from other sources Filter and prioritize

12 12 Context Scenarios How the product can serve a persona s needs Future oriented (not current problem scenarios) From a persona s perspective A story with a beginning, a body, and an end Focuses on positive qualities Litmus test for cool ideas

13 13 Personas System administrator End user Mobile user Scenarios Install the system Add an account Change settings Remove an account Upgrade the system First use of the day Usage during the day Usage from home Mobile use Use from abroad

14 14 Developing a scenario Who What Where When Why How

15 15 From Scenarios to Requirements Context Scenario (snippet) Laura takes a call from Mr. Cowell, who needs to make an appointment for his cat to have a tumor removed. Laura looks him up and sees that he has two cats. Functional Needs (be able to verbs) Look up callers among existing clients See overview information about each client and pet Data Needs (objects nouns) - Call - Client - Appointment - Diagnosis - Procedure - Pet

16

17 17 User Stories As a <type of user>, I want <some goal> so that <some reason>. As a power user, I can specify files or folders to backup based on file size, date created and date modified. As a user, I can indicate folders not to backup so that my backup drive isn't filled up with things I don't need saved.

18 Working Towards Design 18

19 Defining the Data Model 19 Object Definition Relations States Actions Attributes Client A person or organisation whom s pet has been (or will come to) veterinary or technician - Contains one or several pets - Contains one or several invoices - Incomplete (started but lacks info) - Active (current customer) - Archived - Create - Edit - Read - Archive - Find - Name - Address - Phone number - - Account balance - Invoice history Pet An animal that has been to (or has an appointment with) a veterinary or technician - Is part of a customer file - Can contain one or several appointments - Incomplete (started but lacks info) - Active (current customer) - Needs follow-up - Archived - Deceased - Create - Edit - Read - Find - Name - Kind of animal - Age - Sex - Colour - Temper - Health history - Medications - Allergies Appointments An event where the pet is examined - Is part of a customer file - Usually related to an invoice - Incomplete (started but lacks info) - Complete - Create - Edit - Read - Notes - Ordered tests - Diagnoses - Prescriptions - Amount invoiced - Follow-up required

20 20 Functional Elements Office Phone Functional need Functional element Call known contacts or colleagues Contact list on screen Call number that isn t in the contact list Go through messages Manage calls (hold, move) Key pad (physical or virtual) Message display on screen, sound menu for voice control Hold button, move button (physical or virtual)

21 21 Defining the Interaction Framework Create Key Path Scenarios Group functional elements Sketch storyboards Add and change sketches based on more scenarios Adjust according to validation scenarios

22 22 Key Path Scenarios Describes the user s interactions with a product. Focus on the most significant user interactions. How the persona uses the product to achieve goals. Take the context scenario and add functional elements

23 23 A Booking system Persona: Laura, receptionist at the veterinary clinic Goals: Keep calm in chaos Prevent staff and clients from getting upset Keep track of all details Activities: Go through todays appointments Create a file for a new client Check someone in Discharge someone Send invoices Follow up invoice question Follow up unpaid invoices Make appointment Change appointment

24 Functional Elements in the Context Scenario 24 Context Scenario (snippet) Laura takes a call from Mr. Cowell, who needs to make an appointment for his cat to have a tumor removed. Laura looks him up and sees that he has two cats. Functional Needs Look up callers among existing clients See overview information about each client and pet Functional Elements - Area for the client list - Overview for client - Overview for several pets

25 Add the Functional Elements to the Context Scenario 25 Laura takes a call from Mr. Cowell, who needs to make an appointment for his cat to have a tumor removed. Laura finds him in the client list and opens his record to see detail in the client overview display area, which shows that Mr. Cowell has two cats, one of whom is flagged for follow up. She looks at the pet overview display area, sees that Xena needs surgery, and confirms with Mr. Cowell that the procedure is for Xena. She clicks to create a new appointment and chooses the procedure type in the appointment parameters area.

26 26 Client list possible start point for an organizer/workspace pattern? Client list Display area for customer overview Calendar Display area for pet overview Display area for alternative appointments Display area for best appointment Display area for appointment parameters

27 Laura takes a call from Mr. Cowell, who needs to make an appointment for his cat to have a tumor removed. Laura finds him in the client list and opens his record to see detail in the client overview display area, which shows that Mr. Cowell has two cats, one of whom is flagged for follow up. 27

28 28 She looks at the pet overview display area, sees that Xena needs surgery, and confirms with Mr. Cowell that the procedure is for Xena. She clicks to create a new appointment and chooses the procedure type in the appointment parameters area. And so on and on

29 29 Validation Validation Scenarios: What would happen if? Validation with Stakeholders: The result of the framework design is checked with stakeholders to decide how to proceed

30 Elite Inspired Prestigious Unique Exceptional Sleek Advanced Efficient Professional Reliable Trustworthy Powerful Elegant Polished Approachable Solid Competent Helpful Inviting

31

32 @mattiasarvola