These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Sprint / Agile Board
- Features
- Impediments and Risks
Impediments and Risks
Impediments record the reported problem, severity, project and owner.
OverviewOpen Risks×
Sprint / Agile Board · Impediments and Risks
New
Open Risks
Risks
| Risk code | Description | Project | Owner | Probability | Impact | |
|---|---|---|---|---|---|---|
| RC-758 | Open rsk-534 | PRJ-6824 | Low | Low | ||
| RC-238 | Open rsk-160 | PRJ-2237 | Medium | Medium | ||
| RC-875 | Open rsk-245 | PRJ-6159 | High | High | ||
| RC-624 | Open rsk-571 | PRJ-3222 | Low | Low | ||
| RC-564 | Open rsk-477 | PRJ-6454 | Medium | Medium |
6 of 6 records
RC-758Risks · RSK-22985
LowDescriptionOpen rsk-534
ProjectPRJ-6824
ImpactLow
StatusOpen
What you can do
Blockers and exposure
Impediments record the reported problem, severity, project and owner. A new open impediment with severity can be triaged by the workflow, which records an operation receipt. Risks hold probability, impact, mitigation, status and ownership. The triage page brings overdue work, fixed but unverified impediments and open risks into one actionable queue.
How the work is organized
- Starting record. Impediments record the reported problem, severity, project and owner.
- Named owner. Project Manager follows impediments; Delivery Lead owns risk response; Team Member raises a problem.
- Current position. The impediment status, risk mitigation and project owner show who must respond next. The Project Manager checks the triage receipt before handing the impediment to its owner, while the Delivery Lead keeps the risk mitigation under review.
What to agree during setup
Agree who raises an impediment, who owns it and how severity is set. Define when a fixed item is verified before closing it. Give every risk a mitigation owner and revisit open risks during the project check. A failed triage attempt is recorded when severity is missing or the impediment is no longer open.
A Project Manager gives each new impediment a severity before triage and checks the receipt after the status changes. A fixed impediment still needs verification. The Delivery Lead reviews risks separately, using the recorded probability, impact and mitigation to decide which owner must respond before the next project check.
Check the handoff on an actual case
A team member reports an access problem that blocks a story. The Project Manager records severity and the owner, and the open impediment moves to triaged with a receipt. The owner works on the fix, then changes it to fixed. The triage queue still shows it until someone verifies the result. Separately, the Delivery Lead tracks a schedule risk for the same project with probability, impact and mitigation.
The Project Manager checks that the triage receipt points to the same impediment and that its owner can act. When the fix is ready, the team verifies it before closing the record. The Delivery Lead reviews the linked risk separately: a mitigation and owner remain visible even while the story is blocked.
What your team sees
- Open Impediments — Active problems needing an owner and next action.
- Open Risks — Unresolved exposure to review with mitigation.
Follow the work through
See sprint planning for the planning handoff and review and approval for the decision record. Begin with a small project in implementation, then compare the team’s results with the data model.
What it keeps track of
Data model- Projects
- Engagements delivered for an organization, with budget and schedule.
- Stories
- Individual pieces of work assigned to a delivery team member.
- Impediments
- Defects and change items raised against project work.
- Risks
- Project risks with probability, impact, owner and mitigation.
- Operation receipts
- Evidence that a delivery operation was executed.
Who uses it
Permissions- Project Manager
- Follows impediments; Delivery Lead owns risk response; Team Member raises a problem.
Set up Sprint / Agile Board your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.