Software engineering is a most often a team activity.

• Development of complex software systems requires many skills.
• Software exists over a lifetime that may be longer than the participation of any one person.
• Management of teamwork is a fundamental requirement for good software process.

Project Teams

In this course we will organize project teams of 3 or 4 students.

There will be 3 distinguished roles for project teams, plus possibly an additional team member.

• Scrum Master
  • In charge of making sure meetings are organized and happen.
  • Make sure team works together, solves problems, and communicates.
• Product Owner
  • In charge of asking the customer (TA/Instructor) for project clarifications.
  • Takes lead in ensuring all required features for the iteration are being developed.
• Repo Manager
  • In charge of helping everyone work with Git/GitLab.
  • Responsible for accepting merge requests when ready, and helping do code reviews.

• Team Member
  • Like everyone else, shares responsibility for delivering required features.
  • No special duties.

Rotation

• The project will go through several iterations during the term.

• Group members will rotate duties.

Task for Today

• Meet in your groups.
• Decide on the roles that each group member will take for the first iteration.
• Have the Scrum Master send me an email with your group name and list of members and roles.
• Work out your meeting arrangements.
• Discuss the Android/Sudoku or Parabix/CSV application concept.
• Have your Product Owner send one email with a requirements question.