Dive deeper into gitlab
See the latest documentation proposals and Action Plans here
📌 Objective
This issue aims to explore and better understand how we’re currently using GitLab, and to identify improvements that will support our transition away from CCPM toward more agile ways of working (e.g., sprint-based, Kanban, or Scrum workflows, etc).
🔍 Scope
- Review our current GitLab setup, workflows, labels, boards, and issue tracking habits.
- Identify gaps, inefficiencies, or blockers in the current usage.
- Explore how we can improve visibility, traceability, and team alignment through better use of GitLab features.
- Define what meaningful information we need to extract from GitLab to support stakeholder communication (e.g., progress tracking, roadmap alignment, delivery confidence).
- Propose adjustments to workflows or configurations to better suit sprint/Kanban/Scrum methodologies.
🎯 Goals
- Understand how we use GitLab today (in practice, not just intended process).
- Brainstorm improvements to make GitLab work better for our delivery approach.
- Define how we can surface the right information for both team and stakeholders (progress, blockers, forecasts, etc).
- Lay the groundwork for a smoother transition from CCPM to an agile methodology.
✅ Deliverables
- A short report or summary of findings.
- Recommendations or proposals for improving GitLab usage.
- A list of metrics/data points we want to track and how to extract them from GitLab.
- Suggested next steps for process/tools refinement.
Edited by Ana Sousa