Planning canvas and portfolio budget

Planning is sensemaking, not forecasting

A plan is not a promise about the future; it is the best current sense you can make of a moving situation. Treated as a forecast to defend, a plan hardens and drifts from reality. Treated as sensemaking, it stays open to what the work and the stories are telling you. The question is never only "are we on plan?" but "does the plan still fit what we now understand?"

Plan at every altitude, mission, strategy, tactics

Planning fails when the altitudes disconnect: a mission no one can act on, or tactics no one can trace back to why. ScrumDo holds them on one surface so each level stays connected to the one above and below it.

Reframing is a feature, not a failure

Some of the most valuable planning moves are reframes, realizing the problem is not the one you thought you were solving. That only happens safely when the evidence is still attached. When a card still carries the story that created it, a leader can see that the real need was reassurance, not fewer steps, and reframe the work instead of optimizing the wrong thing. ScrumDo keeps the source stories, decisions, and economics next to the plan so a reframe is grounded, not a lurch.

Coherence: one surface instead of three

Planning gets brittle when backlog, staffing, dependencies, and budget live in separate layers that never reconcile. The team can track items but cannot reason about the tradeoffs between value, timing, and capacity. Keeping them in one view is what makes a plan coherent rather than three documents quietly contradicting each other.

• Backlog and sequencing for the planning horizon
• Dependencies and blockers that decide what can actually start
• Releases and the work linked inside them
• Time reporting, budget, and portfolio tradeoffs
• The story evidence and economics behind each choice

Budgeting that gets better, not just tracked

Budgeting improves when spend stays attached to the work it funds. Instead of approving line items and reconstructing reality later, you fund missions and outcomes and can see what each choice is buying, delaying, or starving. Because budget sits next to capacity, dependencies, and economic priority on the same canvas, the tradeoffs get harder to fudge and easier to revisit as the evidence changes.

• Fund outcomes and missions, not just line items.
• See spend, labor, and timing next to the work being accelerated, paused, or deferred.
• Reallocate as evidence moves, instead of defending last quarter’s split.
• Keep an assumption and confidence note on the economics so the math can be questioned later.

Confidence you can defend

False confidence comes from precise-looking numbers with nothing underneath them. Grounded confidence comes from a plan whose claims trace back to evidence, stories, blockers, flow, and economics carried with an explicit confidence level. ScrumDo lets a profile be saved at low confidence as a working hypothesis, because writing down "we are not sure yet" beats a blank that gets treated as certainty. That is how a team earns confidence honestly and stays aligned without pretending to know more than it does.