Track Your Project

You are expected to track your project and all related implementation details in your GitLab project. Your project will consist of project stages (milestones) and user stories assigned to each one (issues).

Milestones

A milestone is a major project activity, with a fixed timeframe.

• Each milestone has a unique name e.g., Proposal or Sprint1.
• Milestones have start and end dates corresponding to the schedule.
• Milestones all end with a submission (demo).

Issues

In GitLab, a user story is represented by an issue.

• The issue serves as a “umbrella” for all work associated with that user story.
• You can create sub-issues for individual items e.g., a user story might have 3-4 related features that are grouped in that user story.
• During planning, you assign user stories to your milestone and to a person who will implement it.

Issues are meant to capture all of the work that you perform for a user story.

• Issues should be initially unassigned. You assign them to a person and a milestone during your planning activities.
• Issues should be updated as work progresses. Ideally, you should be able to understand the state of the project by reviewing the state of the issues attached to the current milestone.
• When you complete the work, you close the issue.

Code branches should be used to stage work-in-progress, and code commits should be coordinated with the issues associated with that commit.