|Module Name||Group Design Project|
|ECTS Weighting ||10 ECTS|
|Semester Taught||Semester 2|
|Module Coordinator/s||Goetz Boterweck|
Module Learning Outcomes
On successful completion of this module, students will be able to:
- Apply Agile development methods;
- Work successfully within an inter-disciplinary development team;
- Appreciate team dynamics and the workflow management needed to achieve successful teamwork;
- Relate to customer needs and requirements and transform these into product tasks;
- Appreciate role of iterative product testing and end user evaluation in a development process;
- Summarize and communicate the work of development teams in succinct presentations and a video.
Instruction will be provided in agile development methodologies and facilities will be provided in order to promote close collaboration between team members. The development of the project will be structured as two product releases as part of the development cycle.
Each week, the current state of progress is reported and discussed, both in the lectures and in the group meetings.
Main topics covered:
- Agile Development;
- Presentation Skills;
- Team dynamics.
Teaching and Learning Methods
The goal of this module is to promote teamwork and to allow students to use their individual skills and experiences within a development team. A key aim is to develop student’s abilities in framing design problems and working iteratively to achieve a working solution Instruction will be provided in Agile development methodologies and facilities will be provided in order to promote close collaboration between team members.
A project mentor will meet with each team weekly and will advise on setting up the team structure including the assignment of roles and responsibilities within the team and on reporting systems both internally and externally.
Weekly peer code and design reviews are a core component of the delivery of the module. These are to encourage a team approach to learning and introduce the practicalities of software quality control.
Class meetings will be devoted primarily to discussion of project progress and issues that arise. As such, class participation is important and will be a part of the grade.
|Assessment Component||Brief Description||Learning Outcomes Addressed||% of Total||Week Set||Week Due|
|Involvement during the class contact hours: lectures and group meetings.||L02, L05||10%|
|Involvement in group activities outside class contact hours, assessed using peer evaluation.||L02, L03||30%|
|Features delivered at each of the two release points, both worth half of the total mark.||L01, L04, L06||60%|
Examination (2 hours, 100%).
Contact Hours and Indicative Student Workload
|Contact Hours (scheduled hours per student over full module), broken down by:||22 hours|
|Tutorial or seminar||22 hours|
|Independent Study (outside scheduled contact hours), broken down by:||180 hours|
|Preparation for classes and review of material (including preparation for examination, if applicable)||180 hours|
|Completion of assessments (including examination, if applicable)||0 hours|
|Total Hours||202 hours|
Recommended Reading List
- Agile Software Development with Scrum, Ken Schwaber & Mike Beedle, Prentice Hall (October 21, 2001).
Prerequisite modules: N/A
Other/alternative non-module prerequisites: An ability to program, at a level typical for Year 4 Computer Science students.