Loading…
—
Each project's latest scored sprint, or fortnight where there is no Jira sprint. The dashed line is the target; the faint one is Green (80). Paler bars are low confidence.
Each pillar as a percentage of what could be checked. A dash means it couldn't be checked (no evidence, or not applicable). Weights: standup 20, planning 15, refinement 10, client review 15, retro 15, Jira 15, roles and artefacts 10.
| Project | Period | Score | Status | Standup | Planning | Refinement | Review | Retro | Jira | Roles | Confidence | Scored | Next report | What's behind it |
|---|
Scores that have since been replaced by a newer sprint or a re-score. Trends fill in here as each sprint closes.
| Scored | Project | Period | Score | Status | Note |
|---|
Each project is scored after its sprint closes and its retro has had time to happen (two working days), from calendars, meeting notes (Gemini, Granola), Slack, Jira, and engineering data from Waydev and Jellyfish read together. Seven pillars are weighted out of 100. Each check is a pass, partial (half marks) or fail; checks that can't be told are left out rather than counted as fails, so a low-confidence score rests on fewer checks. A project can't be Green if a retro was missed or standups ran on fewer than half the working days. Kanban projects skip the sprint-only checks.
Engineering practice, ceremony quality, delivery stability and client artefacts are tracked in each project's email but not scored for the first three sprints.
Scores from the 5 and 6 Nov portfolio used an older weighting that read a few points higher than the live method; each will be replaced when its next sprint is scored.