TDDD26 Development of Interactive Systems
The main part of the course consists of the project work that is carried out in groups. 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.
There are lectures and exercises, supervised project work, as well as supervision meetings to support the project work. Most lectures usually consists of both a "traditional" lecture but also exercises and time to work on the project.
All supervision meetings will begin with a 5 min SCRUM. Then there will be aprox 20 min of discussion on a theme. You should prepare before the meeting by collecting your ideas and material that relate to the theme, and also think about questions you want to discuss with your supervisor. If you for some reason cannot participate you should write 1 A4 page with discussion of the theme and questions for the meeting. This is handed in to the supervisor. If sent by e-mail it should be a text file or pdf file.
There are also unsupervised projectwork in the schedule (marked with an *), those are meeting and development opportunities for the project groups that should always include a SCRUM-meeting.
All activities in the schedule are mandatory to attend. If you cannot attend an activitity, due to for example illness, contact the lecturer/supervisor and group asap and agree on how you will handle this. Below is a timetable that include all the different types of activities and deadlines for the various phases of the project.
During the first week an introduction to agile system development is given. The project groups are formed and each group writes a project specification. All activities except the first lecture are mandatory to attend.
|3/4 13-17||Lecture||Introduction to the course and an overview of Agile methods. Introduction to XP and SCRUM.||Extreme Programming Pocket gudie, by Chromatic, PART 1-6.
Scrum in 5 minutes
|Courseintro.pdf, Agile.pdf, XP.pdf, Scrum.pdf|
|4/4 8-10||Lecture/Exercise||"Extreme hour" exercise||ExtremeHour.pdf|
|4/4 12.00||Deadline||Read about the different roles and possible services and fill in the form to inform the course leader of your interests|
|5/4 13-15||Lecture/Project work||Introduction to the project work. Presentation of project groups. Begin work on project specification.||Questions to discuss||Project.pdf|
|8/4 8.00||Deadline||Hand in project specification to supervisor and customer group||Template for project specification|
During the second week you should prepare for the first iteration, mainly focusing on the design of the system. All activities are mandatory to attend.
|8/4 10-12||Lecture/Project work||Usability work/Interaction design in agile system development||Chris Nodder & Jacob Nielsen. Agile Usability. Best practices for user experience on agile development projects.pdf
Username and password will be distributed by e-mail to course pariticipants
Armitage, J. 2004. Are agile methods good for design?. interactions 11, 1 (Jan. 2004), 14-23. pdf
Patton, J. 2002. Hitting the target: adding interaction design to agile software development. In OOPSLA 2002 Practitioners Reports (Seattle, Washington, November 04 - 08, 2002). pdf
|10/4 13-17||Project work*||Prepare for the design workshop.
Create a virtual workplace, use a tool or wiki, dropbox, excel, google docs.
Decide on technical platform and begin work on backend
|Design workshop outline
A list of tools for agile projects
|11/4 8-10||Supervision||Design workshop and interaction design||
|12/4 13-15||Project work||Design workshop. Some of the group members perform the workshops as designers and some as customers. If one person have both these roles within his/her own group that person should attend two workshops in the different roles.|
A two week iteration with planning game, design, development and testing. Each person should have a total of 15 hours/week to spend on project work, that is a total of 30 hours/iteration.
|15/4 10-12||Lecture/Exercise||More details on planning and acceptance tests. Planning poker exercise.||Planning.pdf|
|17/4 13-15||Project work||Planning game for iteration 1 with the customer. Some of the group members perform the planning game as developers and some as customers.||Planning game|
|17/4 15-17||Project work*||Write acceptance test. Do interaction design. Implement prototype.||Coding of prototype|
|18/4 8-10||Project work*||Write acceptance test. Do interaction design. Implement prototype.|
|19/4 13-15||Project work*||Do interaction design. Implement prototype.|
|22/4 10-12||Lecture/Project work||Introduction to usability testing. Tools and techniques that can be used.
Project groups work on preparing usability testing.
|24/4 13-17||Project work*||Prepare usability testing. Do interaction design. Implement prototype.|
|26/4 13-15||Project work*||Prepare usability testing. Do interaction design. Implement prototype.|
|29/4 10-12||Project work*||Prepare usability testing. Do interaction design. Implement prototype.|
|2/5 8-10||Project work||Testing after iteration 1 with the customer/users. Some of the group members perform the testing as Usability experts/testers and some as users/customers.|
A two week iteration with planning game, design, development and testing. Each person should have a total of 15 hours/week to spend on project work, that is a total of 30 hours/iteration. Designer can design for iteration 3.
|3/5 13-15||Supervision||Brief Retrospective||
|6/5 10-12||Project work||Planning game for iteration 2 with the customer. Some of the group members perform the planning game as developers and some as customers.|
|8/5 13-17||Project work*||Write acceptance test. Do interaction design. Implement prototype.|
|13/5 10-12||Project work*||Do interaction design. Implement prototype.|
|15/5 13-17||Project work*||Do interaction design. Implement prototype.|
|16/5 8-10||Supervision||Open||This is meeting is open for questions from the group. If you do not have any, you can cancel this supervision meeting by e-mailing you supervisor.|
|17/5 13-15||Project work*||Prepare usability testing. Do interaction design. Implement prototype.|
|20/5 10-12||Project work*||Prepare usability testing. Do interaction design. Implement prototype.|
|22/5 13-17||Project work*||Prepare usability testing. Do interaction design. Implement prototype.|
|23/5 8-10||Testing||Testing after iteration 2 with the customer/users. Some of the group members perform the testing as Usability experts/testers and some as users/customers.|
|24/5 13-15||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.|
|24/5 15.00||Deadline||Hand in the code and documentation for the project work at the demo session||For more information see "Examination"|
|31/5 8.00||Deadline||Hand in the individual report.||For more information see "Examination"|
|TBD by project group and supervisor||Supervision||Reflections on project work||
Page responsible: Annika Silvervarg
Last updated: 2013-05-16