How to Automate Scrum Ceremonies in Jira — and Which Parts Should Stay Human
How to automate scrum ceremonies in Jira: automate the mechanics (sprint start/close, rollover, reminders) and keep the judgment human. A ceremony-by-ceremony map.
How to automate scrum ceremonies in Jira: automate the mechanics (sprint start/close, rollover, reminders) and keep the judgment human. A ceremony-by-ceremony map.
How to create a release plan in Jira in six steps: fix versions, scoped epics, velocity-based sprint math, dependency checks, and a forecast that updates itself.
Capacity vs velocity sprint planning is a false choice: velocity sets the ceiling, capacity corrects it for the sprint you actually have. Here’s how to run both in Jira.
Nobody schedules the meeting where the release date changes. It schedules itself — usually for the worst possible week, three...
A vague backlog item is optimism in disguise. How a working Definition of Ready protects the confidence vote — and how a live forecast catches the scope growth that gets through anyway.
The quarterly review had one slide everyone remembers. Version 4.2, committed for March 31, was now April 30 — and...
Critical chain project management was right: manage the buffer, not the task dates. A live 50/85/95% confidence band turns the fever chart into a reading that updates itself.
Resource leveling clears overallocation — and rewrites the capacity assumptions behind your committed release date. See the shift in days, against the 50/85/95% confidence band, in Jira.
Committed vs stretch PI objectives is a confidence decision. See where the line sits on a P50/P85/P95 band from real Jira throughput — and keep it honest after the vote.
How to measure scope creep in agile: baseline the release at commitment, then track scope variance, the burnup scope line, net added work per sprint, and in-ticket growth — and convert creep into days against the committed date.
© 2026 — Divim, Inc. Digital Visual Management Systems and Consulting, Inc.