GitLab PM Associate study plan

Map every major object in the GitLab data model (project, group, subgroup, namespace, user, role) and write a one-line definition for each in your own words

Trace how permissions flow from group membership down to project-level visibility, and note where inherited roles can be overridden

Configure a local GitLab instance or use a free-tier namespace to create two groups, a nested subgroup, and three projects so you can see hierarchy behavior directly

Distinguish the five standard roles by listing two concrete actions each role can and cannot perform

Compare project, group, and instance-level settings and record which ones cascade versus which must be set at each level

Practice locating key features (issues, merge requests, CI/CD, packages, analytics) in the left sidebar and describe the navigation logic out loud

Explain the difference between GitLab.com SaaS tiers and self-managed editions well enough to answer a scenario question about feature availability

Create a personal glossary of 20 platform terms with a usage example for each

Build an issue hierarchy (epic, issue, task) in a test project and link items with blocking and related relationships

Design a labeled board with at least three lists and weighted issues, then move cards through a full workflow

Write two milestone definitions with start and due dates and assign issues to each

Configure a custom issue template and a quick-actions cheat sheet for triage

Set up a roadmap view and explain how epics roll up into it across two milestones

Create burndown and velocity charts by closing issues over several simulated days, then interpret the trend

Draft a short requirements-to-issue traceability example showing how a planning item becomes delivered work

Compare issue boards, lists, and roadmaps and state which planning question each answers best