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 Before This Week
Weekly Progress Check rules
- Be prepared to show your results at the beginning of class.
- Presenting teams are selected randomly each week. The same team may be selected repeatedly.
- If your team is selected and there is no relevant work recorded before the session, 3 points will be deducted. Any relevant demonstrable work avoids the deduction: the weekly score is then between 0 and +3 points, depending on quality and completeness.
- A missing expected result can cause a point deduction only once, but you should still catch up: later work may depend on it, and these results usually contribute to the tasks required for your desired grade. More about salary for tasks
How Weekly Progress Checks work · More about penalty and bonus points
This week's expected results
- Have a runnable version of the application with at least one complete happy-path use case working from start to finish. Be ready to show it during the session: ideally bring a laptop where the application is already set up and can be run, since the classroom PCs may not match your development environment. Also add a few screenshots or a short demo video to the GitLab project so the working result can still be inspected if running it live is difficult.
- Make the project's current status easy to understand in GitLab. Clearly mark which features or issues are already implemented using whatever tracking approach your team uses—for example closed issues, labels, milestones, or a Kanban board—and organize the remaining work into a reasonably concrete roadmap. Explicitly mark features you have decided not to implement, so it is clear what is unfinished, what is still planned, and what is intentionally out of scope.
Notes for tutors:
1: Submitting Issues
Why is this useful for me?
Things you learn and experience in this session will help you to solve the following tasks:
Background
Activities
2: Collaborating on Issues with Others
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: Advanced Aopics
Submitting Issues
Activities
Issue Templates
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