Agile portfolio management in a state agency is the practice of ranking, funding, and adjusting the agency's initiatives on a steady cadence while satisfying the procurement rules, oversight reporting, and legislative mandates that shape every decision. The constraints are real, but they are inputs to the portfolio, not reasons it cannot exist.
Why is the public sector different?
Three things distinguish an agency portfolio from a corporate one. Funding is appropriated by fiscal year and often earmarked, so capacity cannot simply be moved between outcomes. Oversight bodies expect stage-gate reporting on large projects regardless of how the work is actually run. And mandates arrive with dates set by statute, which means the intake door sometimes has to accept work that no ranking would have chosen.
None of this prevents a portfolio from being run on evidence. It does mean the Align practice has to model the constraints explicitly: which capacity is fungible, which is not, and which initiatives are mandated rather than chosen.
How do mandates fit a ranked backlog?
Treat mandated work as pre-ranked. It goes to the top of the backlog with its statutory date, consumes its share of capacity, and the remaining capacity is what the agency actually ranks. Making that split visible on the portfolio view ends the recurring argument about why discretionary initiatives keep slipping: the answer is on the board.
What about procurement?
Vendor contracts fix scope and dates in ways an internal team would not. The portfolio should carry the contract as an initiative with its own capacity line and its own outcome scorecard, so a vendor deliverable is reviewed on the same terms as internal work in the Learn practice. Where contracts allow it, structure deliverables as increments so a scale, sustain, or retire decision has somewhere to land.
How do contractors fit?
Agencies typically bring in contractors. The full-time staff to carry a large program is usually not there, and the operating model never assumed it would be. That is normal, and it is not the problem. The problem shows up when every contractor arrives with a different way of working and a different set of tools.
Eric has been involved in interviewing contractors and in working out what team composition a program actually needs, and that is part of the work. Once people are on board, everyone works from the same framework, toward the same goals and objectives, with connected tools. Contractors who come in as cowboys, each accountable to nobody and each carrying their own tooling, reproduce the gaps and blind spots the agency was trying to fix.
Where do agencies usually start?
A practical start is a single visible portfolio view and an honest count of active initiatives, then outcome scorecards on the largest three or four. You do not need a big program to start. You do need one end-to-end framework that staff and contractors all work from, because that is what makes the count mean the same thing to everyone reading it. A 60-minute Portfolio Clarity Session is a place to start, and it ends with what fits next.