Course syllabus for Agile software project management

Course syllabus adopted 2021-02-26 by Head of Programme (or corresponding).

Overview

  • Swedish nameAgile software project management
  • CodeDAT257
  • Credits7.5 Credits
  • OwnerTKITE
  • Education cycleFirst-cycle
  • Main field of studyComputer Science and Engineering, Software Engineering
  • DepartmentCOMPUTER SCIENCE AND ENGINEERING
  • GradingUG - Pass, Fail

Course round 1

  • Teaching language English
  • Application code 52111
  • Maximum participants60
  • Open for exchange studentsYes

Credit distribution

0119 Project 7.5 c
Grading: UG		7.5 c

In programmes

Examiner

Go to coursepage (Opens in new tab)

Course round 2

  • Teaching language English
  • Application code 52131
  • Open for exchange studentsNo
  • Only students with the course round in the programme overview.

Credit distribution

0119 Project 7.5 c
Grading: UG		 7.5 c

In programmes

Examiner

Go to coursepage (Opens in new tab)

Eligibility

General entry requirements for bachelor's level (first cycle)
Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling the requirements above.

Specific entry requirements

The same as for the programme that owns the course.
Applicants enrolled in a programme at Chalmers where the course is included in the study programme are exempted from fulfilling the requirements above.

Course specific prerequisites

To be eligible for the course the student must have passed courses in programming equivalent to a minimum of 15 credits.

Aim

The course is intended to provide the students with the basic knowledge, and first experience, in the creation of value through software within the scope of a practical project.

Learning outcomes (after completion of the course the student should be able to)

After completion of this course the student should possess the following understanding, skills, abilities and judgement:
Knowledge and understanding, the student should:
  • describe software engineering as an engineering discipline by using relevant terminology
  • describe the relationship between stakeholder, product, and process
Skills and abilities, the student should:
  • specify, implement, and evaluate a system based on what different stakeholders perceive as valuable
  • learn tools and APIs which are relevant for the project in collaboration with the other team members
  • apply a structured software development process as a member of a team
Judgement and approach, the student should:
  • reflect on how the process was applied in a project
  • reflect on the own and the team's learning strategies

Content

The course provides a practical introduction to Software Engineering. Students work on an open problem that is defined by stakeholders outside of the students' team. This means that students will not be able to define the project they work on themselves. By iteratively planning and evaluating their work, they organise themselves in order to reach a joint goal with limited resources. To do this, they apply an agile software development process to structure their work. They specify and evaluate requirements and the collaboration with stakeholders to assure that what is being delivered is perceived as valuable. Students reflect on their own work and learning every week to enable a continuous improvement of their way of working. At the same time, they acquire skills and knowledge in new technologies, tools, and fitting ways to use them in order to provide value to a stakeholder based on the students' own learning strategies.

Organisation

The course is organized as a project where the students work in teams of usually six students to address a real-world software engineering assignment. The teams have weekly supervision meetings. The project is supplemented by exercises and lectures that provide insight into the assignment students are working on and software engineering in general.

Literature

Course literature will be announced on the course webpage.

Examination including compulsory elements

The course is assessed continuously through a weekly report. The report contains both a joint team part and an individual part for each team member which documents the project's progress. The final grade will be based on the last version of the report according to the grading criteria in the course PM. Students thus iteratively and incrementally add to their reflections throughout the project. The content and structure of the report is aligned with the intended learning outcomes. The teachers supply detailed questions and topics to reflect on for each course instance.

The course examiner may assess individual students in other ways than what is stated above if there are special reasons for doing so, for example if a student has a decision from Chalmers on educational support due to disability.