Team Created and Organized

Salary

This task pays a fixed salary of 6 MVP points, plus up to 12 quality points for exceeding the minimum requirements — for a total of 18 points, with a maximum of 3 points per person.

Minimum Viable Product (MVP)

Your first milestone is simple but essential: make sure everyone in the class knows exactly which team they belong to. This is the foundation for all future work — without a clearly formed team, you can’t plan, build, or deliver anything. The goal is to officially form your team in the course’s GitLab space so there is no confusion later.

For the MVP, your team must create a GitLab group under your practice group’s main namespace. The group should use your chosen team name, and your tutor must be added as an Owner. This ensures your tutor can follow your progress and help when needed. You can find GitLab’s guide on creating groups here.

Example: Team 'ByteBusters'

The ByteBusters met during their first session, quickly agreed on a name, and set up their GitLab group right after class. They even added a funny team logo to make it memorable. Now everyone knows exactly where to find each other’s work.

Technical Details

In GitLab, navigate to your practice group’s namespace, create a new subgroup with your team’s name, and invite all members. Assign your tutor as Maintainer so they have full visibility and control. This group will be the home for all your future repositories, issues, and documentation.

Make sure your team space is easy to find — use a clear, consistent naming format. Once the group is ready, check that all members can access it without issues. This avoids technical delays when starting the actual project work.

Quality

Going beyond the MVP means organizing how you will work together. Decide which communication tools you’ll use (e.g., GitLab issues, a chat group, regular calls), when you’ll meet, and how you’ll share updates. Consider the Belbin team roles identified in earlier exercises to assign responsibilities fairly and effectively. Good organization now will save you many headaches later.

A quality setup makes your team efficient from day one: everyone knows where to ask questions, when to expect replies, and how to raise problems. It also means you’ve agreed on working hours, preferred communication channels, and expectations for response time.

Example: Team 'NullPointers'

The NullPointers created their GitLab group, but didn’t stop there — they also set up a weekly 15-minute check-in on Discord and a shared Google Doc for notes. Each member added their Belbin role to their GitLab profile bio so everyone could see each other’s strengths at a glance.