The November 2020 Scrum Guide mentions burn-down charts, burn-up charts, and cumulative flow as practices people use to forecast progress. Then it pulls the rug with a sentence worth taping above any dashboard: in complex work, what will happen is unknown, and only what has already happened may be used for forward-looking decisions. Charts are allowed. Charts that replace observation are not. A personal deadline dashboard goes wrong the same way a vanity burndown goes wrong. It stays green because the inputs are wishes.
You do not need a product team to keep three fields honest. You do need to refuse any field you cannot check against an object that exists today.
Field one: the date someone else can enforce
Write the external date, the one with a consequence if you miss it, separate from any private target. The Guide's Sprint Goal is a commitment that still allows the exact work to flex. Your private target can flex. The external date should not be edited to soothe the row. If there is no external date, say so in the field. "Whenever" is a blank, and blanks cannot turn red.
Next to it, write the planned finish of the last real activity, the day you expect the work itself to be done if nothing new appears. The distance between planned finish and external date is either a reserve or a lie. If you have no reserve, the two dates match and you should know you are promising the ordinary case. The buffer article explains what a named gap is for. The dashboard's only job here is to show both dates. A single date hides whether you are looking at a promise or a hope.
Field two: pace taken from finished work
Schwaber and Sutherland tell Developers, during Sprint Planning, that confidence in a forecast rises when they know their past performance, their upcoming capacity, and their Definition of Done. Past performance is the field people fake. They type the hours they intend to work. Intended hours are a wish. Past performance is a count of finished objects over a recent window.
Pick a unit you can see: pages sent, tickets merged, interviews written up, sections accepted. For the last two or three similar chunks, record how many of that unit you finished per week after meetings, not before. The dashboard stores that rate. Remaining work divided by that rate is the forecast. If the forecast lands after the external date, the row is red. Red is the feature. A dashboard that cannot turn red is motivational wallpaper, and wallpaper does not change a date.
Do not average in a heroic week unless heroic weeks are your normal capacity. One late night that produced double output will poison the rate and repaint the row green. The Guide's line about using only what has happened is not permission to cherry-pick the happiest week. It is permission to ignore the fantasy of next week. If you have never done this kind of work, the rate field should say "unknown," and the forecast should be a check-in, not a delivery promise. Unknown is honest. Zero is a different claim.
Field three: the next physical action
The Sprint Backlog, in the Guide, is a visible, real-time picture of the work Developers plan to do to hit the Sprint Goal, detailed enough to inspect at the Daily Scrum. Your third field is the personal version of that picture, shrunk to one line: the next physical action that moves the object. "Work on the report" cannot be inspected. "Open the source sheet and type the three column headers" can. When the action is done, replace the line. If the line has been the same for three days, the row is red even if the dates look fine, because the pace field is about to be wrong and the dashboard should say so before the calendar does.
A stalled action line is also where scope shows up. If the line changed from "send the draft" to "add the appendix a stakeholder mentioned," you did not make progress. You replaced the object. Either the date fields move or the appendix leaves. Leaving both untouched is how a green row lies.
A row, invented so you can see the shape
This table is an illustrative example. The project is fictional. Do not treat the hours as advice about your work.
| Field | What it says today | Why it is red or not |
|---|---|---|
| External date | 30 October, board packet | Not editable for comfort |
| Planned finish | 24 October | Six days of named gap. Not a place to add a section |
| Recent pace | Two accepted sections per week, last three weeks | Four sections remain, so two weeks of pace, which fits before the 24th only if this week stays clear |
| Next action | Same line since Monday: "clean up the intro" | Red. The intro is not on the stop rule. The next action should be the unfinished section |
The row is red because of the action line, not because the dates look impossible. That is the point of three fields. Any one of them can contradict the mood. If you only track the external date, this packet looks fine until the 29th. If you only track mood, "clean up the intro" feels like taste. The pace field says the remaining sections need clear weeks you may already have sold. The meeting ledger on the meeting-debt page is how you check whether those weeks are real. The lookback on the two-week page is when you read the red row out loud and pick one change.
What to leave off the screen
Leave off motivational scores, streaks, and any number you cannot recompute from files. Leave off a health metric. This dashboard is not a medical device, a financial plan, or a performance review. It will not tell you whether you are a good employee. It will tell you whether the date, the recent pace, and the next action agree. When they do not, the honest dashboard stays uncomfortable until you change one of the three. Changing the font color is not one of the three.
Schwaber and Sutherland note that forecasts like burn-downs do not replace empiricism. A spreadsheet with these fields is in that family: useful, optional, and dangerous when the cells are typed to match the hope. If maintaining the sheet takes longer than the next action, you have built a fourth project. Go back to a single page with three lines. The format is not the honesty. The willingness to write "unknown" and "red" is the honesty.
Update the pace field when something finishes, not every morning. Morning updates tempt you to log intentions. Evening updates can only log what exists. The Guide's inspection cadence is frequent enough to catch drift and short enough to leave time for the work. Daily is plenty. Hourly is an avoidance costume.
A small promise, and its edge
Three honest fields will not finish the packet. They will make it harder to be surprised by a miss you could have seen in the pace. They fail when you lie in the cells, when the work has no countable unit, or when someone else owns the date and will not hear red. In that last case the dashboard's output is a sentence you send, not a color you soothe yourself with. If they will not hear it, you still know. Knowing is not the same as controlling. Do not let the sheet imply control you do not have.
If you opened your list right now, which row would turn red if the pace cell had to be copied from the last three finished weeks instead of from the week you are hoping for?
Guide used for the three fields
- Schwaber, K., & Sutherland, J. (2020, November). The Scrum Guide. Forecasting with burn-downs, Sprint Planning and past performance, and the Sprint Backlog as a visible plan. scrumguides.org/scrum-guide.html