TDDD26 Development of Interactive Systems

Project

The purpose of the project work is to practice methods for user involvement and system development, in particular XP and PD/ID. This involves building and evaluating working prototypes, but the focus should be on the process and your experiences working with the methods.

Groups

Here are the project groups

Roles

Each group serve as both customer/user to another group's system and developers of their own system. This means that all participants have at least two roles in the project group. One is as customer/user of another group's systems. One or more roles are related to development of their own system.

In the group you divide the participants so that 2-3 persons are customers and the rest are users.	Customers shall: Participate in activities with developers to specify and design system Participate in planning games Write acceptance tests At least one person should be available for the developers with short notice and participate in at least one coding session as on-site-customer	Users shall: Participate in at least two test sessions at the end of the iterations
In the group you divide the participants so that 2-3 persons are usability experts/interaction designers/testers and the rest are developers. One person can also be designated as project leader/scrum master/etc in addition to having another role (which will be smaller than the others).	Usability experts/interaction designers/testers shall: Specifiy and design the system together with the users Plan and execute two test sessions with end-users at the end of each iteration	Developers shall: Plan and execute two planning games. The first includes both release planning and iterationplanning, the second just iteration planning. Implement a working prototype during each iteration, using several XP practices
Project leader/Scrum master This role is optional in the project group. The group decides if they want to have this role and what the responsibilities are for this role. This should however not be a full time role, but should complement one of the other roles.

Each person should have a total of 15 hours/week to spend on project work, that is a total of 30 hours/iteration.

Project ideas

The task for the project work is to develop a new concept for existing web services. The developed prototype should be inovative and offer new types of functionality. Example of systems are:

• Media, a system that helps display and organise digitial media, for example photos, videos, music.
• Datingservice, a system that supports dating, as a web based service or in other forms that the customers request.
• Webshop/Auction, a system for people or companies to sell/buy products or services.

Outline

The project consist of the following phases:

• Project start-up:
  • Fill in the form to inform the course leader of your interests
  • The course leader announce project groups
  • Project group makes a project specification
• Sprint/Iteration 0
  • Decide on technical platform
  • Design workshop with users
  • Design for Sprint/Iteration 1
  • Create a virtual workplace
• Sprint/Iteration 1
  • Planning game: release planning and iteration planning
  • Write acceptance test
  • Design for Sprint/Iteration 2
  • Implement prototype
  • Testing: acceptance test and usability testing
• Sprint/Iteration 2
  • Brief retrospective on Sprint/Iteration 1
  • Planning game: iteration planning
  • Design for Sprint/Iteration 3
  • Write acceptance test
  • Implement prototype
  • Testing: acceptance test and usability testing
  • Demonstration

Activities

Here you can find further instructions for the different activities:

• Project start-up
• Specificatin of project
• Design activities with users
• Planning game
• Coding of prototype
• Testing

Project demonstration

Each group will demonstrate their system. The supervisors and other students have the opportunity to use your system and ask questions about the system and how it has been developed. There should be a person available by your system to answer question at all time, but you should change places regularly so all group members can test the other systems too.

Deadlines

• Week 11 Examiner presents group, Groups discuss and formulate an initial specification of the system. The specification is given to customers and supervisors on Monday week 12.
• Week 12 Developers have interviews/design workshops etc with users to further specify the system
• Week 13 Planning game on Wednesday.
• Week 13 and 16 Implementation of prototype iteration 1 (and other related activities, for example SCRUM meetings, and meetings and discussions with supervisor)
• Week 17 Test of prototype 1 with users on Wednesday, Brief retrospective with supervisors on Thursday, Planning game on Friday.
• Week 18-19Implementation of prototype iteration 2 (and other related activities, for example SCRUM meetings, and meetings and discussions with supervisor)
• Week 19 Test of prototype 2 with users on Thursday. Demonstration of prototype on Friday.
• Week 19 Hand in of project on Friday at 17.00.
• Week 20 Hand in of individual report on Wednesday at 13.00.
• Week 20 Meeting with supervisors on Wednesday

Page responsible: Annika Silvervarg
Last updated: 2012-02-22