Portfolio work types

Classify portfolio work by strategic intent, not just status.

ScrumDo helps leaders separate table stakes, spoilers, differentiators, cost reducers, discovery, improvement, support, and delivery work before everything collapses into one priority queue.

Portfolio hierarchy with typed work flowing into strategy and release decisions
How it works

ScrumDo is a work management system with the decision context kept on the work.

Teams still plan and deliver with familiar boards, cards, releases, blockers, and reviews. ScrumDo keeps the decision context on the work: stories, work type, flow policy, budget, Cost of Delay, release commitments, and decision records.

Teams still plan and deliver with familiar boards, cards, releases, blockers, and reviews. The difference is that ScrumDo lets the organization attach the context that usually gets scattered across decks and spreadsheets: customer or worker stories, portfolio work type, flow policy, budget assumptions, Cost of Delay, release commitments, and decision records. Leaders can then inspect the work from strategy, economics, evidence, and delivery angles without treating any one metric as automatic truth.

Strategic language

A portfolio needs more than priority labels.

Kanban and Enterprise Services Planning emphasize fitness for purpose, business risk, and explicit policies. ScrumDo turns that thinking into usable portfolio language for everyday planning.

Table Stakes

Required baseline work: regulatory, contractual, reliability, market entry, or minimum viable parity.

Spoilers

Bounded parity work that neutralizes a competitor edge without pretending to be differentiation.

Differentiators

Strategic bets tied to a value hypothesis, market position, retention, expansion, or revenue.

Cost Reducers

Work with a cost baseline, savings hypothesis, and payback conversation attached.

Treatment vs type

Work type is not class of service.

Work type describes the business shape of the work. Class of service describes how the system should treat it. Keeping those concepts separate makes portfolio decisions clearer.

A bug can be standard or urgent

The type says it is defect work; class of service explains the treatment.

A feature can be a fixed-date commitment

The type says it is value-building work; class of service explains the schedule risk.

A differentiator can still wait

Strategic importance does not automatically mean immediate pull priority.

Practice those communities already use

Grounded in delivery practice those communities already use.

ScrumDo is informed by Scrum, Kanban, SAFe Lean Portfolio Management, and flow economics. The product is the work system. The methods stay yours.

Bring evidence, economics, and flow to your organization.

Explore how ScrumDo connects portfolio strategy, team delivery, and governed AI on one inspectable record.

ScrumDo Business

Turn portfolio planning into an evidence-backed operating loop.

Use strategy, flow, budget, release planning, and decisions together instead of splitting them across decks, tickets, spreadsheets, and chat.