Sprint learnings that record themselves.
When a hotfix closes inside a sprint, the lesson is logged for you, with the severity and area filled in from the issue. Add the rest from retro meetings, incidents, notes or by hand.
A fix marked as a hotfix, moved to done inside a sprint, becomes a to-improve entry by itself. The severity comes from the priority and the area from the epic, and nobody had to remember it a fortnight later.
The learning ledger
Five categories, each with its source.
Went well, to improve, actions, learnings and decisions. Every entry shows where it came from, and a dot marks how serious it was. Actions have a button that turns them into real work. You will find all of this inside the sprint retro.
Standups matched themselves off the calendar all fortnightmeeting
Deal base currency not recalculated on rate changeFinance HQhotfix
Written by the database when the hotfix closed. Nobody typed it.Realtime filter missed updates without replica identityPlatformhotfix
Import mapping reverted on a second passDataincident
Add a rate-change trigger test to the finance suitemanualCreate issue
Scan the commit history back to March and seed the ledgermanualCreate issue
Two conflicting CHECKs meant the marker had to be its own columnProjectsnote
Hotfix stays a boolean on the issue, not an issue typemeeting
A hotfix logs its own learning.
Hotfixes log themselves.
Mark a fix as a hotfix and the lesson is captured the moment the work is done.
- Mark a fix as a hotfix on the issue
- The learning is logged for you when the fix is done inside a sprint
- Severity and area are filled in from the issue automatically
- Add learnings from a retro meeting, an incident, a note or by hand
- Every entry shows where it came from
- The same fix is never logged twice
Turn an action into an issue.
Anything the team agrees to do becomes a real issue in the next sprint, with an epic and dates.
- Turn an action into an issue in one step
- It goes into the next sprint with dates already set
- Group learnings by category to keep the retro focused
- Track your hotfix rate by area and by severity
- Fill the ledger with earlier learnings from work you have already shipped
Access
Who can do what.
Anybody on the sprint can log a learning or mark a fix as a hotfix. Turning actions into committed work, and filling in learnings from past work, belong to whoever runs delivery.
See the learnings for any sprint you can view.
Log a learning, and mark a fix as a hotfix.
Turn an action into an issue in the next sprint.
Fill in learnings from past work and decide what gets measured.
Admin is the highest role and is not limited by the permission grid, so give it only to the few people who genuinely need it.
One hotfix, start to finish
A hotfix at two in the morning, and a learning nobody had to write.
The only thing anybody did was drag the card to done. The learning wrote itself with the right severity and the right area, waited two weeks, and became an issue in the next sprint the moment the team agreed on it.
Raised as an issue and marked as a hotfix on the board.