Week 10: Incremental Development (Imp.)
Goal
The goal of this week's session is that students experience what it means to collaborate on projects not designed by them from the scratch. They have to learn to understand the project contribution rules.
Expected Results until this Week
We will discuss expected results during the class on this week. So please make sure to be prepared! More about penalty and bonus points- Your team’s repository already contains working source code with identifiable modules or features.
- You can point out which parts of the system are functionally implemented, even if not yet polished or complete.
| Title | Duration |
|---|---|
| Issue Templates | 30 minutes |
| Submitting Issues | 30 minutes |
| Collaborating on Issues with Others | 30 minutes |
Notes for tutors:
1: Issue Templates (30 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
- https://docs.gitlab.com/user/project/description_templates/
- Auto-populate fields with variables and quick actions: https://docs.gitlab.com/user/project/quick_actions/
- How to Think When Writing Good Issues
Activities
2: Submitting Issues (30 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
Activities
3: Collaborating on Issues with Others (30 minutes)
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
Activities
Collaboration Count as Feature Implementation
Collaborating on issues from other teams counts towards your team's feature implementation requirements for this milestone.
- Tutor has to be notified about the collaboration in advance in person.
- Your team will get double points for each successfully completed collaboration compared to working on your own issues.
- The hosting team will get halve points for each successfully completed collaboration compared to working on your own issues.
- The results have to be presented in a joint demo session.
Successful completion will be decided by the tutor in the role of the customer. See grading details for context.
Example — Cross-Team Feature Collaboration
Scenario: Two teams collaborate on a data-export feature originally valued at 24 points.
Teams and Roles
| Team | Role | Feature Price | Bonus Logic | Points Earned |
|---|---|---|---|---|
| Team A | Provider (implements) | 24 | Double reward for successful collaboration | 48 points |
| Team B | Host (integrates) | 24 | Half of reward for hospitible environment | 12 points |
Tutor’s Role: Acts as the customer to validate the result in a joint demo.
The feature must be functional, integrated, and clearly presented by both sides together.
Result Summary
- Provider earns double for sharing valuable work.
- Host earns a smaller share for successful integration and coordination.
Both succeed or both fail
Both teams must successfully complete their parts of the collaboration for either to earn points. If one team fails to deliver, neither team earns points for that collaboration. This ensures mutual accountability and encourages effective teamwork between teams, which is the goal of this exercise.