The Framework
PPM4Agile is a portfolio operating system for organizations whose strategy and delivery have come apart. It runs on four connected practices, Align, Focus, Deliver, and Learn: Align decides what matters, Focus proves you can deliver it, Deliver executes the committed slice, and Learn measures what shipped and feeds the next decision. Six operational drivers carry the practices: workflow, meetings, people, metrics, artifacts, and the tools pipeline.
The problem
PPM4Agile exists for portfolios where the effort is real but the system that directs it is missing. The symptoms look the same in public and private organizations, whatever the industry.
Agile has been around for more than 20 years, and many organizations have already tried it. They have sent people through Scrum or SAFe training and bought tools like Jira, Rally, or VersionOne. Dates still slip because those pieces were never connected. One group works in one tool and the next group in another, so someone syncs them by hand, errors creep in, and blind spots open up. Requests are written down however each group likes, so months later nobody can trace what was asked for. Teams may know Scrum well, but nobody is working from one framework that runs end to end, from choosing projects to measuring their value, so the silos stay. Eric Fullerton built PPM4Agile so people understand how the roles and processes connect: who hands what to whom, and what good input and output look like at each step. With that shared picture, the training and the tools you already paid for can finally pull in the same direction. The PPM4Agile course teaches it differently, too. Certification training is the starting point, not the ending point. This course has you build your own portfolio’s operating system, one phase at a time, so you finish with a playbook you can take back to your organization.
Three decisions
Investment, scope, and value. They are connected, so if you focus on one and skip the others, no amount of agile will fix it. This is how Eric thinks about any portfolio, and the course’s four phases tie back to it: Portfolio Development (Align) answers the investment decision, Planning and Execution (Focus and Deliver) answer the scope decision, and Evaluation, Value & Learning (Learn) answers the value decision and feeds the next investment decision.
Investment decision
Scope decision
Value decision
The loop
Each practice gives the next one what it needs to start, and each sits behind one of the course’s four phases. Align (Portfolio Development) settles what matters. Focus (Planning) turns one piece of it into a plan the teams agree to. Deliver (Execution) finishes the work and shows what it did. Learn (Evaluation, Value & Learning) tells the next round of portfolio decisions what that changes.
Portfolio Development
Turn ideas and requests into an approved, prioritized portfolio, with the reasons written down.
Explore Align →Planning
Turn one approved project into a plan someone can actually execute.
Explore Focus →Execution
Execute the committed slice and finish it, with a real hand-off to operations.
Explore Deliver →Evaluation, Value & Learning
Measure what shipped against the goals it was funded for, then scale, sustain, or retire it.
Explore Learn →Align answers
How do we decide what actually belongs in the portfolio?Focus answers
Can this plan survive reality?Deliver answers
Why is everyone busy and nothing is finishing?Learn answers
How do we know any of this worked?Audience
The framework is written for the people who select, plan, and coordinate the portfolio. Everyone else benefits from knowing their inputs and outputs within it.
The difference
A framework rollout usually starts with ceremonies and roles. PPM4Agile starts with the decisions and adds only the structure needed to hold them.
A portfolio operating system is the set of decisions, cadences, and evidence an organization uses to choose work, plan it, deliver it, and learn from it. It sits upstream of the projects. Most organizations already have one, but it is implicit: intake happens through whoever asks loudest, capacity is assumed rather than measured, and status is reported as activity. PPM4Agile makes the system explicit. Align turns ideas, requests, and work already in flight into an approved and prioritized portfolio, and writes down the reasons for every yes and every no. Focus takes one approved project and proves it can be delivered by the people you actually have. Deliver executes that committed slice and hands operations something they can actually support. Learn measures what shipped against the goals it was funded for and feeds the answer into the next Align decision. Six operational drivers carry all of it, and configuring them is what turns a set of good intentions into a system. The result is a loop leaders can run, and decisions they can defend when priorities are challenged. You don’t need a transformation program to start, but you do need one end-to-end framework everyone works from.
Because everything you add later rests on it. Think of the portfolio as a house. The first floor is the end-to-end pipeline: how projects are chosen, funded, planned, built, released, and measured, and who hands what to whom along the way. Even a team of five needs that floor: a clear priority and a path from a funded idea to feedback from real customers. Scaling adds stories: more teams, more projects, and eventually other departments, such as marketing or HR, coordinating their own work the same way. If the first floor isn’t stable when you start adding stories, you are putting more weight on an unstable structure, and what you get is chaos at a larger scale. So PPM4Agile starts by getting the basic pipeline, roles, and processes working for the teams you already have. Once that holds, each new team, project, or department works from the same framework instead of inventing its own.
Operational drivers
Six things decide whether it works. The course shows you how to set each one up. There is a seventh piece, and it is the one most rollouts skip.
PPM4Agile Course
A self-paced course on the PPM4Agile framework, in four phases from portfolio development to evaluation and learning. Each lesson pairs the material with an example of it done well in a case study, then has you apply it to your own organization and build a playbook to bring back.
No. PPM4Agile operates one level up, at the portfolio, and is framework-neutral. Teams can keep running SAFe, Scrum, Kanban, or nothing in particular. The four practices decide what those teams work on, what a plan has to prove before anyone commits to it, and whether the results justified the investment. See the comparison with SAFe Lean Portfolio Management for the detail.
It depends on your organization and how open your people are to changing how they work, so there is no standard timeline. The first result is an Align decision: an approved, prioritized portfolio with the rationale written down. Focus starts when one of those projects is ready to plan, and Deliver and Learn follow as that project moves through execution and into production. You don’t need a transformation program first. You do need everyone working from the same end-to-end framework.
The four practices form a loop, so each depends on the one before it. You can start with Align alone and see value, but without Learn the loop never closes and the portfolio drifts back to activity-based reporting. Each pass through the loop is one iteration, and a sensible first pass runs on a single project before you widen it.
Yes. Procurement rules, oversight bodies, and legislative mandates are treated as inputs to Align, not as reasons the system cannot work. Over his career Eric has worked with the California Department of Public Health, as well as private companies. Industry isn’t what decides fit; what matters is running a lot of IT projects that need coordinating.
Read about Align to see what it gets you, then take the self-paced course or book a Portfolio Clarity Session to apply it to your own portfolio.
Start with a 60-minute conversation about how your portfolio runs today.
