The RAID Log: The Register Is Fine. The Refresh Rate Isn’t.
A RAID log records risks, assumptions, issues and dependencies — as of the last edit. Why the R and the D go stale, and how to keep them live against a committed release date in Jira.
Managing Technical Debt: The Quiet Tax on a Committed Release Date
Technical debt is a capacity change in slow motion — no calendar event, just throughput drifting down after the vote. How to see it move a committed release date in days, in Jira, and renegotiate before the slip.
Crashing vs Fast-Tracking: Measure the Gap Before You Compress the Schedule
Crashing vs fast tracking: what each schedule compression move really costs, and how to size the gap — in days, against a 50/85/95% confidence band — before you pick a rescue.
Scrum of Scrums: Make the Cross-Team Dependency Meeting Count
Scrum of scrums works when it runs on a live dependency map instead of status theater. A working agenda, the anti-patterns — and how Jira teams keep it to 15 minutes.
Scope Creep vs Change: Stop Confusing the Two in Release Planning
Scope creep vs change: creep is unacknowledged scope growth; change is a visible, negotiated decision. How to tell them apart — and keep your Jira release date honest.
Individual Capacity Planning in Jira: Plan People, Not Averages
Jira’s Summer Release makes individual capacity planning native. What the new Capacity view covers — and how to plan per-person availability, skills, and part-time staff beyond the team average.
Student Syndrome & Parkinson’s Law: The Two Habits That Eat Your Schedule Buffer
Key Takeaways Student syndrome, named by Goldratt, is the habit of starting a task as late as its built-in safety...
The Bus Factor: When One Person’s Absence Moves a Committed Release Date
A bus factor of one means a single calendar entry — leave, illness, a resignation — can move a committed release date. See the capacity change in days, against the 50/85/95% confidence band, in Jira.
Sprint Spillover: How Carryover Quietly Erodes a Committed Release Date
Sprint spillover is normal flow — until it compounds unseen. How carryover quietly moves a committed release date, and how to see the drift in days against your 50/85/95% confidence band in Jira.
External Dependencies: When Your Release Date Lives in Someone Else’s Backlog
External dependencies — vendor deliverables, partner APIs, hardware lead times — erode committed release dates from outside your Jira. Give the promise a ticket, put it on the critical path, and renegotiate before the slip.