Startup
Project – Purpose
Annika Silvervarg
• To practice methods for user involvement and system
development, in particular XP, SCRUM and UX/ID
• This includes designing, building and evaluating
working prototypes, but the focus should be on the
process and your experiences working with the
methods and tools
Project – Prototype
• The prototype should have so much functionality that
the user experience is representative of the future
system
• It is better to focus on implementing a small part with
high functionality than many parts with low or no
functionality
• You can implement your prototype using the
programming language of your choice
Project – Supervision
• Contact with supervisors
– meeting will have different themes
– bring material and ideas for discussion
– opportunity to discuss progress and small problems
• For bigger problems or questions book a meeting with
supervisor
Project – Teams
• The project is done in interdisciplinary teams with
students from different educations
• Each group is both developers of a system and
customers of another system
• Persons have different roles:
• In the group you divide the participants so that 2-3 persons are
customers and the rest are users
• In the group you divide the participants so that 2 persons are
Interaction designers and the rest (4-5) are Developers
• One person can also be designated as scrum master in addition to
having another role (which will be smaller than the others)
• (You can switch roles after iteration1)
Roles – Customer
• Role-play
– be engaged in the specification and creation of the system
– portrait a non-technical person
• Change your mind at least once during the project
• Answer questions promptly
• Participate in design activities with Interaction
designers
• Participate in planning games
• Write acceptance tests
• Participate in sprint demos/acceptance testing
1
Roles – Interaction designer
• Specifiy/Design the system together with the customers
–
–
–
–
–
–
Workshop with customers
Create and evaluate LoFi prototypes
Personas?
Storyboarding?
Wireframes?
HiFi prototypes/GUI programming?
• Plan and execute usability test sessions and acceptance
test sessions
• Help the customer during planning games
• Help the customer write acceptance tests based on
usability?
Roles – Developer
• Perform two planning games
– The first includes both release planning and iteration
planning,
– the second just iteration planning
• Implement a working prototype during each iteration,
using several XP practices:
–
–
–
–
Testdriven programming
Pair programming
Continous integration
and more…
Roles – Scrum master
• Is a combination of coach, fixer and gatekeeper
• Helps the team do the best work they possibly can
• Is responsible for making sure a team lives by the
values and practices of Scrum
• Holds an evaluation meeting after each sprint – a
Sprint retrospective – during which experiences and
conclusions are reviewed
• Has less authority than the traditional project leader
Project outline
• Iterations/Sprint
– Startup
• Set up developer team
• Specify system as customers
– Sprint 0
• Initial design and workshop with customers
• Set up workplace
• Set up technical plattform
– Sprint 1 and Sprint 2
• Design/Usability activities
• Implementation
Start up
• Who does what? Divide the roles!
• Where and when to work together?
– Interaction design, front end development and/or back-end
development in the same room at the same time?
– Mobile and/or Virtual workplace?
• What technical platforms and programming language
are you going to use?
• What XP practises are you going to follow/use?
• What ID activities and tools are you going to use?
• Remember to plan for Scrum stand up meetings often!
Project specification
• The project specification is a vision of the future
system that should have a reasonable deliverable at
the end of the course
• You CAN use design levels for structure:
– Vision - What is the basic idea of the system?
– Goal - What is the goal of the system?
– Services - What should the user be able to do with the
system? What kind of services does the system offer?
– Usability goals - How should the system be experienced?
– Physical form - In what form should the system exist?
– Special demands on security, hardware and performance?
2
Product statement
• Vision and Goal can be formulated as a product
statement
Material etc
• http://www.ida.liu.se/~TDDD26/project/index.en.shtml
• http://www.ida.liu.se/~TDDD26/info/material.en.shtml
– Ex: trakz.nl is a trustworthy online music store, we are
apersonal and passionate about music!
– Template: For (target customer) who (statement of need or
opportunity) the (product name) is a (product category) that
(key benefit, compelling reason to buy)
3