2014-03-30
Sprint 0
Interaction design
Sprint 0
Annika Silvervarg
•
•
•
•
•
•
•
•
Strategic intake & research
• Market and end-user
– Competition?
– Market?
– End-users?
• Brand
– Defined brand?
– ”tone-of-voice”?
– Corporate visual identity?
Product statement workshop
• Introduction
– Stakeholders (people)
– Reason for and goal of workshop
Strategic intake & research
Product statement
Design koncept
Technical solution outline
Practical agreements
Setting up the ”room”
Definition of done
Start on Product backlog
Product statement
• Template: For (target customer) who (statement of
need or opportunity) the (product name) is a (product
category) that (key benefit, compelling reason to buy)
• Example: trakz.nl is a trustworthy online music store,
we are apersonal and passionate about music!
Design koncept
• Graphic profile
• Conceptual design
• Goal gathering on post its
– Identify clusters
• Split in pairs an write statements
• Discuss in whole group
• Decide on statement
1
2014-03-30
Practical agreement
•
•
•
•
•
•
When do you work?
Where do you work?
Contact information, e-mail, phonenumbers….
When do you have stand-up meetings (and how)?
When do you demo (test) and with whom?
When and how do you do the retrospective?
Setting up the ”room”
•
•
•
•
Hardware
The room
Supplies
Software
– Dropbox?
– GIT, SVN,…
• Scrumboard
• Trello, wiki, excel, google docs,…
Definition of Done
• Technical requirements
–
–
–
–
Start on product backlog
• More on this in the next lecture
Devices?
Browsers?
Documentation?
How tested?
• User experience
– How does it feel?
– Tests with external people?
• Customer acceptance
– Who decides when done is done?
Interaction design
…in an agile system development process
Interaction design – When?
2
2014-03-30
Interaction design – When?
Interaction design in parallell
Interaction design in Agile
Interaction design
• ID people are bridges, between users and developers
• Concept(ual) design (Sprint 0)
– Become part of the team, rather than remaining aloof
– Own the user experience
• ID work is early and flexible
• ID work happens in parallell
• ID work – quick-and-dirty
– What will be designed?
– Why will it be designed?
• General design (Sprint 0,1)
– How should the main features be designed?
• Detail design (Sprint1,2,….)
Conceptual design (ISO 9241-210)
• Understand and specify the context of use through
user studies
• Specify the user requirements
• Produce design solutions, concept sketches and
storyboards
• Evaluate the designs against requirements
User studies
•
•
•
•
•
Interviews
Observations
Personas
Task analysis
Scenarios
• More info
– Courses: TDDD59, TDDD60,…
– http://www.usability.gov
– http://infodesign.com.au/usabilityresources/
3
2014-03-30
Persona
sheet
Persona example
• www.ida.liu.se/
~matar/
tools.en.shtml
Design
•
•
•
•
Who does, what, when, why and how?
Actions and objects
Temporal, spatial and logical structure
Interaction, navigation, use of functions, how to
manipulate content
• Look & feel
Design Concept sheet
Design
•
•
•
•
Sketches
Wireframes
Storyboards
Prototypes
–
–
–
–
Paper/LoFi
MidFi
Hi-Fi
Tools: Powerpoint, HTML-editors, Balsamiq, Director,
Jbuilder
Design Concept sheet cont.
4
2014-03-30
Design Concept sheet cont.
Storyboard
Wireframe
Diverge before Converge!
• Remeber to explore different alternatives!
Interaction design – What/When?
Design workshop
• Interaction designers, (developers), customers and
users work together to design a solution
• Most effective early in the design process, when ideas
can be less constrained by existing code or other
infrastructure
• The workshop participants can be (ideally 8 persons):
–
–
–
–
–
Representative users
Business representatives (customers)
Developers
Interactions designers
A facilitator
5
2014-03-30
Design workshops –
Example agenda
• Introductions – Participants introduce themselves
The facilitator can set the tone by being first to do so
• Usability presentation – This is an opportunity to get
participants thinking about usability
• Objectives and Expectations. Be clear about the
purpose of the workshop, and identify what each
participant expects as an outcome
• Identify issues – The issues may be with a system to
be replaced, or with the domain in general
Design workshops –
Example agenda
• Design goals – With the issues in mind, identify the
usability goals that the system must meet
• Scenarios – serve to centre the discussion on the
actual users. Have participants read and refine the
scenarios
• Paper prototyping – Split the group in two and have
each spend a short amount of time (no more than 20
minutes) working independently on solutions that
address the selected scenario or scenarios
Design workshops –
Example agenda
• Combine designs – Each group presents its design
and the group discusses relative merits
• Further design work - Depending on the outcome of
the first prototyping session, decide how to use the
remaining time most effectively
• At the end of the workshop, review expectations and
objectives to ensure they have been met
• Document the outcomes as soon as possible
Plan ID activities and
design workshop
• Activities
–
–
–
–
–
–
User studies
Design workshop(s)
Sketching
Story boarding
Paper prototyping
…
• Plan design workshop
–
–
–
–
Persons to attend
Focus of workshop
Outline workshop
Create material
– (Usability testing later)
6