risk-analysis

To identify product risks early, systematically structure and rank them across product, delivery, and systemic domains by impact and likelihood before finalizing epics and stories. This generates prioritized risk reports with mitigation guidance.

You need delivery risk analysis during pre-execution planning, following QA failures, or after major scope changes. Analyzing risks at these planning phases prevents delivery failures by structuring severity rankings and mitigation strategies before issues derail plans.

Yes, risk reporting includes an anti-collision guard to prevent overwrites. Generating risk reports to specific artefact paths ensures existing risk analysis files remain protected while structuring newly identified systemic and delivery risks.

The best way to structure systemic risks after major scope changes is reading existing artefacts and memory context, then analyzing risks across systemic domains. This generates structured risk reports with severity rankings and mitigation guidance.

Generate risk reports for QA iterations by reading artefacts and memory, then writing new reports with an anti-collision guard. This prevents overwriting previous risk analysis data while structuring newly identified product and delivery risks.

No, risk analysis requires no external dependencies or components to function. It systematically identifies and structures risks by reading provided artefacts and memory context, then generating prioritized risk reports independently.