RELATED IDEAS
Risk identification and tracking
I appreciate the recent release of the Project workspace. However, a big part of Project Management is Risk Tracking and Mitigation. I would like to be able to identify risks at a Project or Product line level and tag those risks on Release and Features, and even possibly Goals and Initiatives.
While a Release might have a specific risk that can be added now using custom fields, I want to be able to identify a risk and associate multiple data elements with that risk. This includes comprehensive reporting on the Risk Level, Risk Name, Description, Mitigation plan, and Releases/Features/Initiatives that are impacted.
1
MERGED
© 2024 Aha! Labs Inc.•All rights reserved
Any update on this request? This is standard reporting for any project
We are struggling with custom fields/layouts to track Risks and feel this needs to be built out as a feature in Aha! to track along with releases. Our stakeholders expect to see that PMs are tracking the date the risk was opened, risk level, mitigation, status, etc. along with a history/timestamp so that the information is not lost. When creating custom fields for "Risk factors" we are running into limitations with using the note v. text box v. excel fields and then pulling that into reports and dashboards is a bit of a formatting nightmare. In addition, there isn't history so PMs could accidentally override the information they've previously added and we would not know it.
Yes, please!
It would be really helpful to be able to track both Risks and Issues across the various record types in the data model.
Absolutely. We actually are using a project workspace to accomplish this through a bit of creative use. We use the "ideas" as risks and the "features" as issues. We use score cards to measure our risk (probability*impact) but have to have two in order to capture our initial risk assessment and then current risk assessment.
If a risk is realized, it can be promoted to an issue that is actively being mitigated. The one downside is "shipping" the release. We've found ways to categorize most of the work to be able to close out and archive but it is a little weird. But it does allow us to put our entire program's risks and issues in one place and then link to the appropriate work in other workspaces/features that are affected. The functionality is just about there with some tweaking it would be great.
Agree this is needed. In addition to dependency tracking, risk identification and management is a feature that will greatly increase Aha's value.