Release Planning

The Kano model sorts features into must-be, performance and attractive before the confidence vote. After it, a late must-be or a promoted delighter lands as scope. Read what each reclassification costs the committed date, in days.

A matrix organization gives every engineer two managers. The allocation is agreed before the confidence vote; the functional side moves people after it. Read what each move costs the committed date, in days.

Team Topologies sets team types and interaction modes to cut hand-offs. After the vote, crossings change mode. Read what each one costs the committed date, in days.

Descoping is the agreed answer to scope creep, but most teams do it late, when the cheap cuts are half-built. Price each cut in days against the committed date.

Resource availability is confirmed at the confidence vote: who is in, which days, which holidays. It changes the week after, and the sheet never says what that costs the committed date, in days.

A project network diagram maps every known task and arrow on planning day. After the vote new arrows appear, and the drawing never says what they cost the committed date, in days.

An agile spike buys the team an answer. The answer usually arrives as new stories inside the committed release, after the vote, with no change request and no new date.

Resource utilization shows how busy a team is, as a percentage. It never says how much of that time went to the release, or what a rise costs the committed date, in days.

A dependency matrix marks who needs what from whom at planning. It never says what a new mark, or an old one that ages, costs the committed release date, in days.

Jira Align pricing for 2026: Atlassian sells Align in the Strategy Collection at $77,400 a year for 1-50 users. What that includes, and what release and capacity planning costs as a Jira app.