Software Development Project 1

Welcome to the Software Development Project 1 course! 👋

During this course, we will learn how to manage the software development process and how to work as a member of a software development team. We will learn these skills in practice by developing a software development project in a software development team consisting of 4-5 students.

Each team will be developing a project described here. The project is a web application implemented with Java programming language using the Spring Boot framework. Also, React is used as a frontend technology. The development of the project is split into three two-week iterations called Sprints. Each Sprint has high-level requirements, but teams should make most of the technical decisions themselves. The project starts on week three. For more information about the course, read the course description.

The course follows a weekly schedule. There are weekly topics that are covered in weekly sessions on on Tuesdays at 14:00 - 16:00 and Thursdays at 14:00 - 16:00 in classroom 5006 for the implementation SOF005AS3A-3012 and on Wednesdays at 11:45 - 13:45 and Wednesdays at 8:00 - 10:00 in classroom 4012 for the implementation SOF005AS3AE-3004. Attendance of the weekly sessions is mandatory. On the first two weeks, there are exercises on each week that need to be submitted before the submission deadline. On the third week, we start working on the project in teams.

Teacher

Kalle Ilves (kalle.ilves@haaga-helia.fi)

The course has a Teams team for all course related discussions. When you have trouble with an exercise or any other questions related to the course, feel free to ask about it in Teams. You can find the link for joining the Teams team on Moodle.

Assessment

The first week’s exercises in Introduction to software development projects need to be submitted before the deadline to confirm course participation.

The assessment is based on the team’s project and the personal contributions of a team member.

The project assessment is based on the following aspects:

  • Technical implementation: required features should be implemented and they should work as intended without major bugs
  • Project management: project management-related documents (e.g. backlogs) should be well organized and kept up-to-date throughout the project
  • Documentation: required technical documents should be written and they should correctly describe the technical implementation
  • Following the schedule: each Sprint has requirements and the project should advance during each Sprint

The team can earn up to 40 from the project.

Each team member’s personal assessment is based on the following aspects:

  • Activity in team work: Attendance and active presence during team meetings and communication with team members outside the meetings
  • Technical contributions: amount of working code written or active participation in the writing process of the code (for example pair-programming)
  • Project management and documentation contributions: Backlog management, efforts to improve the process (for example in Retrospectives), writing project related documentation
  • Exercise submissions: at least 18 of the first two week’s exercises have to be completed to pass the course
  • The final report written at the end of the course

The personal assessment is done based on the teacher’s observations and peer reviews from the team members. Each team member can earn up to 20 points based on their personal efforts towards the project and their exercise submissions from the first two weeks.

The final grade (1-5) is composed of the project points (maximum of 40 points) and the personal points (maximum of 20 points).

The following are necessary to pass the course:

  • At least 16 of the first two week’s exercises have to be completed
  • Written peer review for each team member
  • Passing grade from the peer reviews
  • Written final report