0
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.
0
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.
0
Key Takeaways Student syndrome, named by Goldratt, is the habit of starting a task as late as its built-in safety […]
0
Six names on the roster doesn’t mean six people. A step-by-step method for calculating real sprint capacity when staff are part-time or detailed elsewhere.
0
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.
0
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.
0
Compute real team capacity — leave, details, allocations — before committing a sprint. A 60-minute agenda and worked example for government agile teams.
0
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.
0
The instinctive rescue for a slipping release — adding people — is a capacity change, and Brooks’s Law says it cuts the wrong way first. How to see the real cost in days against your committed release date in Jira.
0
Fixed budgets, fiscal-year deadlines, and shrinking teams make capacity-based sprint planning a survival skill for government agile teams. Here’s the math.