Team Setup

Introduction Round

Have an introduction round. To make it more fun, start with one student that interviews another one, then move to the next student, so that each one gets interviewed and each one poses the questions once.

You can ask the following:

(Or anything else you want to know.)

Team Reflection Document

Find Your Teams Channel

In the Team for the course you find a channel for each team. (It may be listed under hidden channels.)

Use this (public) channel when you meet and share your video, so others can join your meeting. This is a bit like working together in a big room and you can visit the table of another team.

Store all your documents in the files section of your team's channel.

Create a Team Reflection Document

Throughout the entire semester, you must maintain a team reflection document. This is a single document, one per team, in which you reflect over teamwork and roles. After each team activity you visit this document and add an entry for the week.

The team reflection document is also part of your final portfolio. It is not graded, but contributes as context for grading all other deliveries.

Team Roles for This Week

Have a quick look again at the team roles that you have read through during the preparation.

Time Check

Try to briefly get an overview of today's tasks, and come up with a rough time plan. Don't forget to schedule some breaks, too.

Find a Team Name

Picture

Create a Week Entry

Create an entry for this week as a new section.

Attendance

Note the attendance of the team members during the week. If someone is missing, try to find out why and make a note.

We will come back to the team reflection document at the end.

Task: Use Piazza

We use Piazza as the forum to ask and answer questions, both from teams or individually. To get started and into the habit of using Piazza:

Task: Learning Goals Relevance

It is very likely that you will find the learning goals of this course useful in your later career, no matter what your detailed role is. For simplicity, we can distinguish between three different roles: developer, product owner, and project manager.

In the following, you should estimate how relevant the learning goals of this course are for the different roles.

More Detailed Role Descriptions

For this activity, we work with three simplified roles. In reality, they can be more subtle and vague, and some roles are combined. What is important for now is that you start getting aware that different roles during development exist, and that they have different tasks and responsibilities, and therefore have different motivations, interests and require different skills.

Role: Developers

Developers usually work in a team of several developers. This will also be most likely your first position when you work in industry as an engineers. With respect to software, it often means that the task involve programming or building a system, but it can also mean to work on requirements with customers, do testing or other technical tasks. Developers are the one with technical expertise and know about how to build a system or product, but are not necessarily the ones answering why a certain product should be built or which features it should have.

Role: Product Owner

The product owner is usually a single person, with the responsibility to maximize the value of the product to its owner, which usually pay for the development in the first place. Note that the owners of a system are distinct from its users.

Role: Project Manager

The project manager is usually a single person, with the responsibility to manage the development team. This means to assign tasks and plan ahead, so that all resources are available. The project manager usually does not any detailed technical work, which is delegated to the developers.

Example for Roles: A software house with 100 employees gets a contract to develop a new information system for bus stops in a city. The bus operator pays for the software development and will then own the system, as part of their contract with the system. The users of the application will be the persons taking the bus, but also some of the employees of the bus operator. The development team consists of three developers, which do the programming of the backend, the monitors at the bus stops and integrate and update code for a mobile application. The product owner is also employed at ABC software, but is responsible for several products and keeps contact with the bus operator. In ABC software, the role of the project manager is also fulfilled by the product owner, but for the product owner this feels like a different task and has sometimes troubles of keeping the two apart, which is a bit stressful.

Copy the DOCX with your final answer into the general channel / Files and folder for this unit. (This is why you should change the XX in the filename to your team name.) Done!

Balances in Teamwork

Ideally, your team works in a balanced way. Below with examples for balances you should be aware of:

These are just examples of balances.

Copy the PPTX with your final answer into the general channel / Files and deliveries folder for this unit. Done!

Team Reflection for This Unit

It may seem like an overhead to reflect already now during the setup and with these relatively simple tasks. But this team reflection should become a routine from now on. Fill out the section for today's week:

Roles

Reflect about the following points:

Improvements

Reflect about the following points:

Today's Performance

Reflect about the following points:

Individual Reflection

Each week you should in addition complete an individual reflection, that makes up your individual reflection diary. These reflections will help you to collect material for the individual deliveries. To ensure progress during the semester and also as some form of feedback to us, the individual reflection is kicked off with an individual reflection survey.

Checklist

Deliver via Teams:

Deliver via Forms: