All articles
Track risks, dependencies and decisions
Keep what could stop delivery, what you're waiting on, and why scope changed on the product record, where the team will actually see it.
What you'll end up with
A Needs attention list that surfaces overdue dependencies and at-risk milestones without anyone compiling it.
Why it matters
Risk logs kept in spreadsheets go stale because they sit apart from the work. In Ondule, risks, dependencies and decisions are records on the product, next to the milestones and epics they affect, so an overdue dependency shows up on its own and the reason behind every scope change is one click away.
Before you start
- A product with milestones and epics
Log risks and issues
Open Risks & Issues on the product and press Add item.
Set Type to Risk. Write a clear Title, choose the Owner, and set Impact, Likelihood and a Review by date. Under Relationships, link the Milestone or Epic it affects, then press Create item.
If the risk actually happens, open it, press Edit and change Type to Issue.
Risks & Issues for Pulse Analytics.
Record dependencies
Open Dependencies and press New dependency.
In Needs, choose the work that requires something, for example "Dashboard builder". In From, choose the Ondule work or named party it depends on, for example "Event schema contract". Set the Owner on the other side and a Due date, then press Create dependency.
Dependencies, with overdue ones flagged.
Record decisions
Open Decisions and press New decision.
Write the Decision, for example "Ship templates before exports". Add the Context, Options considered and Rationale, then set Decided by and Date.
Under Related work, link the Milestone or Epic it affects, then press Record decision.
Review it weekly
Open the product or department Overview and work through Needs attention from the top.
Resolve, reassign or re-date each item.
How it connects
Where the risk sits among the other records.
Troubleshooting
Why isn't my dependency in Needs attention?
Only overdue dependencies appear: ones with a due date in the past that aren't resolved. A dependency with no due date, or one that's still in date, stays on the Dependencies page instead.
What's the difference between a risk and an issue?
A risk might happen. An issue already has.
Can a dependency point to another product's work?
Yes. The From side can be another product, or an epic, milestone or issue in another product. It can also be a named party outside Ondule, such as a supplier or another team.
Updated · Still stuck? Email hello@ondule.com.