IdeaIntake, Hypothesis, Research
Score a backlog
Rank the backlog by value per unit of cost. Score each candidate on six inputs, choose one of four weightings, and the page ranks your backlog with the same formula as the repository's scorer. A telemetry readiness of 0 blocks a candidate until its data is collected, and a mandate due within 90 days moves to the front.
Tips
- Select a ranked row to set its scores against each scale and to see its arithmetic, step by step.
- Paste your own backlog as CSV. The note under the box lists the columns, and this browser keeps the backlog between visits.
- Copy link saves your weights in the address, so you can share an ordering.
The method behind it Prioritization
On this page
Weights
Backlog
One candidate per line: id, name, T, I, B, R, E, C, an optional mandate due date (YYYY-MM-DD), and an optional marginal coverage state (first, stronger, equal; blank means first). The repository's scorer derives that state from the live set; here you supply it, because the page has no live set to compare against. Evidence lines are enforced in the repo, so the page ranks whatever you paste.
Leave a score blank and the candidate waits at the end of the table until you set it there. A file this page exported pastes back, and this browser keeps the backlog between visits.
Select a row to set its scores against the wording of each scale and to see how its score was reached.
| # | Candidate | Score |
|---|
Scales
Same formula as score.py in the repo. The backlog stays in this browser, and nothing is sent anywhere. Rendered from framework.json v0.136.0, CC BY-NC 4.0.