Portfolio planning
Articles
Build on your mastery of planning, estimation, team capacity, and resource allocation. Our product builders share the principles we've developed—often by discovering what doesn't work first.
Loading articles…
The delivery hasn't slipped. The work has outgrown the plan
A due date three months out can stay green while the work beneath it already finishes later. The slip is real; it just lives between the plan and the backlog.
Read article →
Jira isn't broken. It's doing its job.
Jira tracks work one team at a time, by design. Whether a group of teams still fits the estimate its plan was built on is a different question, and it needs a different kind of check.
Read article →
Two estimates who have never met
The early estimate and the work beneath it live in the same portfolio. What happens when nobody brings the two together?
Read article →
A backlog isn't a plan
A backlog records what exists. A plan states what can happen, when, and with which teams. Treating them as the same thing hides work that no forecast accounts for.
Read article →Deriving the t-shirt size from story points tells you nothing
Automating an epic's t-shirt size from its rolled-up story points looks tidy. It makes the high-level estimate and the detail identical, so they can never disagree.
Read article →
Why are we still rebuilding the plan after the PI starts?
Once a PI starts, reviewing the ART plan often means rebuilding a spreadsheet first. Capasight brings the group’s work together so reviews can focus on decisions.
Read article →No articles match your search. Try a different title, topic or author.