Syllabus academic year 2009/2010
(Created 2009-08-11.)

Higher education credits: 9. Grading scale: UG. Level: A (Second level). Language of instruction: The course will be given in Swedish. Optional for: C4, C4da, D4, D4ps. Course coordinator: Görel Hedin,, Inst f datavetenskap. Prerequisites: EDAA01 Programming - Second Course or EDA027 Algorithms and Data Structures, Object-Oriented Modelling (EDA061 or EDAF10), and EDA260 Software Development in Teams - Project. The number of participants is limited to 20 Selection criteria: The number of participants is approximately 20. The exact number depends on the number of participants in the course EDA260. Assessment: All course items are compulsory. Grades given are Pass or Not Pass. To pass the student must have completed the theoretical and practical parts of the course and completed an in-depth study. Further information: Limited number of participants, approximately 24. Home page:

The aim of the course is to give knowledge of and practical experience from how to lead and coach a software development team. The course also gives more in-depth knowledge about principles for agile software development.

Knowledge and understanding
For a passing grade the student must

Skills and abilities
For a passing grade the student must

The course consists of three parts covering two study periods: a theory part (first study period), a practicum part, and an in-depth study (both during the second study period). The theory part consists of lectures and discussions on practices within iterative development such as planning, customer and user involvement, software architecture, design, and documentation. The theory part also includes an exercise and some minor home assignments as a preparation for the discussions.

In the practicum part each student will coach a programming team of students taking the course EDA260. This part includes development of an initial prototype and architecture for the product, guidance for how to coach, planning meetings with the team, coaching of the team during development sessions, and documenting the architecture of the final product. Coaching may be done in pairs.

In the in-depth study the students write a paper (individually or jointly with another student) on a specific topic, based both on literature studies and experience from the coaching sessions. The papers are presented as a written report and are also presented at a seminar. The students also review each others reports and presentations.

One of those two books will be used:
R. Jeffries et al: Extreme Programming Installed. Addison Wesley 2001. ISBN: 0-201-70842-6
(Handbook of Extreme Programming).
chromatic: Extreme Programming Pocket Guide. O´Reilly 2003. ISBN: 0-596-00485-0.
Additional material, e.g.articles will be distributed by the department.