“Are we funding value streams, or still funding projects?”
Every part of lean portfolio practice — strategy and investment funding, agile portfolio operations and lean governance — on one model: value stream budgets and guardrails, participatory budgeting, the portfolio kanban, epics and lean business cases, and the events that steer them. Run it as SAFe describes it, or run it on its own over product lines and value streams that have never heard of a release train. Budgets tie to the ledger, epics trace to strategy and spend, and a new SAFe version arrives as changes you approve. Dot prepares each portfolio event from the record; the portfolio council still makes every call.
Runs in
Covers
Funding value streams, not projects
The pressure
Most companies adopt lean portfolio management in the language first. Value streams appear on a slide, but budgets are still approved per project, guardrails live in a policy document and epics are justified once and never checked. Finance keeps its own numbers. The budgeting event runs on spreadsheets assembled the week before, and the portfolio kanban sits in a tool that knows nothing about the money.
What it looks like today
Full coverage
The guardrails, the kanban, the business cases and the events all sit beside the money, the strategy and the architecture they answer to.
Built for SAFe 6.0 LPM — and for lean portfolios run without SAFe
Connect the portfolio to strategy, and fund it.
The four guardrails, on the budgets they govern.
Move the right epics, and keep value flowing.
Spend, measure and comply without stage gates.
Every portfolio event starts from the record.
Lean portfolio practice on its own terms.
What changes
Funding project by project
Value stream budgets with guardrails, beside any project budgets — never added together
A portfolio kanban that knows nothing about the money
Every epic with its business case, value stream budget and actual spend on the card
Business cases approved once
MVP hypotheses measured, with each persevere-or-pivot decision recorded
Participatory budgeting from spreadsheets
Funding scenarios compared on the plan of record before the event
Strategic investment funding
Draft a different split of the value stream budgets and set it beside the approved plan: capital deployed, the share going to transformation, which objectives are funded, the people required and what has to stop to make room. Versions of one plan are compared, never summed — so participatory budgeting starts from the trade-offs, not from a spreadsheet.
Where other tools stop
The kanban usually lives in an agile portfolio tool and the budget in a planning tool, so nobody can see what a different split of the value stream budgets would fund — or stop.
Flexed to how you run
Few portfolios move to lean funding all at once, and many never adopt the rest of SAFe. Dotwork meets the portfolio where it is — projects, value streams or both.
With or without SAFe
Run lean budgets, guardrails and the portfolio kanban inside SAFe, or over product lines and persistent teams with no trains at all.
Hybrid funding
Keep project budgets for the work that still needs them, beside value stream budgets — held on separate paths and never double-counted.
Your states and thresholds
Rename kanban states, set your own approval threshold and define your own horizons, with the standard practice underneath.
Adopt in stages
Start with the portfolio kanban and lean business cases, then move one value stream to a lean budget and add guardrails as trust grows.
Across SAFe versions
When Scaled Agile publishes a new version, the renames and new practices are proposed against your portfolio for approval. Past budgets, cases and decisions keep the names and structure they were made under.
The Agile Program Management Office became the Value Management Office
Relabeled — its work of measuring the flow of value reads the same records
OKRs added for strategic themes, epics and lean business cases
Themes, epics and cases linked to key results in the OKR Hub
Value stream management made a portfolio responsibility
Value streams as first-class records, with their budgets and their flow
Flow metrics, including flow predictability, under Measure and Grow
Read per value stream from the delivery data you already connect
Program Increment renamed Planning Interval
Relabeled across the planning cadence — past intervals keep their history
Every framework, one model
Lean portfolio management decides where the money goes. OKRs say what it should move, TBM says what it costs and delivery metrics say whether it is flowing. Here those four answers come from the same records, not four tools.
Scaled Agile’s operating model for AI
When LPM runs inside SAFe, trains and increments draw on the same value stream budgets.
Explore AI-Native SAFeGoals tied to funded work
Strategic themes carry key results, so the portfolio is judged on what it moves.
Explore OKRsTeams funded around products
Products funded as value streams, so moving between the two is a change of view.
Explore Product Operating ModelIT spend taxonomy
Spend against each value stream budget is the cost TBM has already reconciled.
Explore TBMDelivery flow and performance metrics
Each value stream’s flow time and load, read beside what it was funded to deliver.
Explore Flow & DORAActivity-based costing · rolling forecasts · Beyond Budgeting
Beyond Budgeting’s rolling forecasts behind dynamic value stream budgets.
Explore Cost & Planning MethodsAI-native LPM
The work that eats a portfolio office’s month — assembling the budgeting pack, chasing business cases, reconciling budgets with finance — is drafted for you. Recommendations stop at the lean portfolio manager, epic owner or business owner who owns the decision.
Checks each ask against its value stream’s budget, flags budgets with no guardrail on record and keeps lean and project budgets on separate paths.
Drafts alternative splits of the value stream budgets and compares each with the approved plan — what it funds, who it needs and what it stops.
Reads the portfolio kanban and calls out epics that are stalled, unfunded or missing a lean business case.
Drafts the lean business case from the epic and the model — hypothesis, MVP, cost, the value stream it draws on and the key results it should move.
Keeps estimated benefit apart from realized benefit and shows which MVPs are proving their hypothesis.
Follows each strategic theme through epics and value stream budgets to booked cost, and flags chains that stop at the plan.
Drafts the review pre-read from the records — budgets against guardrails, flow on the kanban, business cases and benefits.
Keeps what was funded, deferred, pivoted or stopped, with the reasons, for the next event to start from.
Where it runs in Dotwork
Dotwork does not ask you to adopt a new method. The framework becomes a view over the same model these solutions already read and write.
Govern & Deliver
“Is the work we are doing still the work we meant to fund?”
ExploreFund & Optimize
“Can we still move money before the period closes?”
ExploreGovern & Deliver
“Are we building what customers need — and is it paying off?”
ExploreHow it compares
Portfolio suites run the kanban and the budgets after a long setup. Spreadsheets run the budgeting event. LPM on Dotwork runs the practice with or without SAFe and connects the portfolio to the strategy, cost and architecture around it.
| Capability | SPM & agile portfolio suites | Spreadsheets & slides | LPM on Dotwork |
|---|---|---|---|
| Portfolio kanban with epics and lean business cases | Partly | ||
| Value stream budgets and guardrails | Partly | ||
| WSJF and cost-of-delay prioritization | Partly | ||
| Participatory budgeting with scenarios compared | Partly | Partly | |
| Lean portfolio practice without SAFe | Partly | ||
| Value stream budgets matched to finance’s books | Partly | ||
| Project and lean budgets held apart — never double-counted | Partly | ||
| MVP hypotheses checked against realized benefit | Partly | ||
| SAFe version changes with past budgets and decisions kept | Partly | ||
| Wired to strategy, cost and architecture |
Who it is for
“Is every value stream funded, bounded by a guardrail and able to cover its asks?
“Are value stream budgets and project budgets ever counted twice?
“Does my business case still hold, and what did the MVP prove?
“Which epics in my value stream earn the next dollar?
“Which enablers does the portfolio need, and what will they cost?
“Is value flowing, or is work piling up in the funnel?
Before you buy
How to get a number instead of a pitch.
1
Good answer · Yes — on one screen, matched to what finance booked.
Bad answer · The budget in finance’s tool and the epics in another.
2
Good answer · Yes — value streams, guardrails and the kanban work on their own, beside projects.
Bad answer · Only after the trains and increments are configured.
3
Good answer · The MVP hypothesis is measured, and persevere-or-pivot is a recorded decision.
Bad answer · It is attached to the epic and never opened again.
More in Strategy & Delivery
Strategy & Delivery
The methods that turn strategy into funded, delivered work.
The model underneath
Steer, Fund & Optimize and Govern & Deliver all read and write the same Enterprise Operating Model. The first module you license builds the model. Every module after it adds context instead of another silo — and Dotwork AI reads all of it, stopping where the decision is yours.
See the Enterprise Operating Model© 2025-2026 Dotwork, Inc. All rights reserved.