DFE-Digital / DFE-Digital/compass
Define prioritisation schema (criteria and weights)
Open
@andyjones81 is already working on this.
Since Dec 5, 2025.
- Dominant language
- HTML
- Stars
- 0
- Forks
- 1
- Avg merge
- 1m
- Merged PRs (30d)
- 3
Description
User story
As a Central Ops manager, I need a standard prioritisation framework so we can compare demand consistently across portfolios.
Description
Define the prioritisation criteria, scales, and optional weights used to score and rank DemandRequests.
Acceptance criteria
- List of prioritisation criteria agreed (e.g. strategic alignment, user impact, statutory/legal driver, risk reduction, readiness, cost/resource impact)
- Each criterion has:
- A clear description
- A defined scale (e.g. 1–5 or low/medium/high mapped to numeric values)
- Optional weighting for each criterion is defined and documented (if weighting is used)
- Formula for overall priority score is documented (e.g. weighted sum)
- Criteria and weights stored as configuration, not hard-coded in multiple places
- Framework reviewed and agreed with key stakeholders (Central Ops, leadership)
Non-functional
- Approach is flexible enough to add or adjust criteria in future without major code changes
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.