Managing Risk, Project Wins, and Business Development

Mitigating Risk via RAID Issue

• The RAID, Risks, Actions, Issues, and Decisions is our way to ensure a single source of truth for project risk & resolution
• It is where our internal project stakeholders and leadership can reference the latest project information when the project is trending or sitting in a Y/R health status
• The RAID is automatically created when the PM creates the CPR template. First step is to rename template “RAID - Customer - SOW/PO#
• While the RAID is created, managed, and reported by the PM, the internal & Customer team is encouraged to be updated the RAID as we work through Project challenges and mitigations
• Example

Reporting on Risk via RAID

• Use the label “Escalated” to create immediate attention as it impacts the progress of the project. For internal visibility, the RAID link is included in the Top Customer Report when a project is Y/R
• Escalated items can be found here.

Tracking Project Wins, Business Development Items, and Customer Stories

The process of a internal project retrospective is started when the project starts. It is a collection of team celebration, lessons learned, what could be improved, questions, comments, assets create. This in an internal-only issue and the Gitlab team is encouraged to gather learnings and celebrations throughout the Project.

• The Internal retro issue lives within the internal Customer EPIC and is created when the Epic is created, the latest template can be found at the issue level, and here
• PMs to make sure this issue is linked in the internal Project slack channel

Reporting on Customer Wins, Lessons Learned, and Delivery Kit Updates

• Customer Stories, Project Wins, and Completed Internal Retro report can be found here.
• Needed Delivery Kit Updates can be found here.
• For tracking lessons learned around scoping, PS process, PS Product, Support, or misaligned expectations, reference here.

View page source - Edit this page - please contribute.