Blog Highlights
- The agile phases of project management (Envision, Speculate, Explore, Adapt, Close) combine iterative delivery with clear governance. Phases 3 and 4 repeat, creating the learning loops that make agile delivery adaptive rather than reactive. They only deliver that adaptiveness when the system tracking them is as connected as the phases themselves.
- The real failure isn’t at the sprint ceremonies but rather at the infrastructure that supports these phases: No financial baseline at Envision, no cost-rate insight at Speculate, no billing linkage at Explore, no portfolio view at Adapt and no data capture at Close.
- The research by McKinsey that we have from its enterprise agility study reported that at the operational performance level -speed of delivery, for example, increased anywhere from 30% to 50%. That improvement was achieved through the Explore and Adapt feedback loop that works very quickly to identify out-of-whack requirements.
- PMI research consistently shows that organizations waste a significant portion of every dollar they invest in projects on low performance, most of it from projects that repeat estimation errors that the Close phase overlooked the first time around.
- Kytes connects every agile phase to financial and resource data in one platform, so agile project planning software and agile project management software are not separate tools bolted together.
QUICK ANSWER
The agile stages of project management are five defined steps: Envision, Speculate, Explore, Adapt and Close. Unlike waterfall stages that follow one another (one closes, another begins), Phases 3 and 4 of agile methodology are repeated over and over again, in the order of a sprint, which involves Phases 3 and 4 of agile followed by a new set of Phases 3 and 4 of agile; In a to every phase, there is a new planning and new delivery, creating a cycle that continues until you reach your vision. The challenge with an IT services business isn’t in the phases. It’s in the pipes: no system linking the completion of a sprint to billing, resource costs to planning, lessons learned to estimating.
Why Do Agile Phases Still Break Down at the Portfolio Level?
An IT services company managing a 700-person IT services organization had been doing agile for three years. His teams were familiar with Scrum ceremonies. Sprints were two weeks.
Retrospectives occurred.
Visible board. But when the executive team asked what projects would be completed this quarter he had no answer he could give in real time.
Sprint health and portfolio health are two different things. His teams were tracking the agile phases of project management at the delivery level. But they had no platform to link phase-level performance metrics to resource expenses, billing position, or margin. Every Adapt phase had a planning round that assumed unconfirmed budget headroom; every Close phase had lessons-learned that sat in a document no one read.
The phases of agile project management were happening. The supporting infrastructure was not. This is precisely where sprints end and invoices begin: the point where the delivery cycle ends and the financial cycle should begin, but does not.
What Are the Agile Phases of Project Management?
The phases were codified in the Adaptive Project Framework (APF), a project management methodology devised by project management consultant Robert Wysocki. The five phases of PMI’s Agile Certified Practitioner (PMI-ACP) body of knowledge, one of several categories of agile methodology available to enterprise project management offices (PMOs), is based on that model.
Agile is now the predominant project management methodology in IT services delivery. Digital.ai’s State of Agile Report-the oldest report on the adoption of agile practices in IT services delivery-included the transition from outlier to ubiquitous state a decade ago, giving traditional project management’s highly structured process a new, flexible shape.
The Five Phases, One by One
Phase 1: Envision. Define the Vision Before You Build Anything
Envision is the phase in which the project purpose, boundaries of scope, and conditions of satisfaction are defined. This phase encompasses four things, the project vision statement (not features but business goal), core team, stakeholders, and conditions of satisfaction, (client-agreed upon success criteria that are different than requirements, requirements are what is to be constructed, conditions of satisfaction are the what will be delivered), and the initial budget connected to real resource cost rates.
The most common failure of Envision is calling it a kickoff meeting or having a phase that is not a phase. With insufficiently specified vision, the agile team gets iteration-itis. Agile project planning software enables the vision, conditions of satisfaction, and initial budget to be captured in a single system, so every phase thereafter begins with a common starting point. Without an agile project planning system, the starting point is stored in a person’s memory, and you know how long that lasts.
Phase 2: Speculate. Plan Without Locking Scope
Speculate generates a flexible plan that anticipates all the needs will shift. It includes: the initial product backlog in the form of a numbered, prioritized list of user stories, sprint definition (size, team, target velocity), a release plan that provides stakeholders with a forecast of when the first working version of the product will be completed, and resource estimation based on actual cost rates instead of headcount.
A resource plan that figures out 12 bodies without factoring in the costs is not a plan. It’s an assumption and, more often than not, that assumption turns into a margin surprise two sprints down the road.
Phase 3: Explore. Deliver in Sprints, Learn in Every Cycle
Explore is the real work: the sprints of plan, build, review, plan, build, review. Each sprint delivers a working increment reviewed with stakeholders, giving you feedback to power the next cycle. That “gain” you’ve seen is there because of Explore: the short feedback loop gives you the opportunity to adjust your requirements at relatively low cost.
The Four Scrum Ceremonies in the Explore Phase
Sprint Planning– The team agrees on items to be added to the backlog, on scope, and on the sprint goal. In an IT services organization managing several client relationships, sprint planning takes into consideration the availability of resources on each active engagement, not only the team you are working with.
Daily Standup– 15-minute sync where team members go through three questions: what did I complete, what will I work on today, what is blocking me. This brings blockers to the surface in a more manageable time frame and while they can still be addressed within the sprint.
Sprint Review-The team presents its finished work to stakeholders and receives input that feeds into the backlog of the next sprint. This is the main customer collaboration activity in the agile stages.
Sprint Retrospective-The team looks back on what went well, what didn’t, and what can change for the next iteration. Retrospectives place continuous improvement in the delivery and not just in the review post-mortem that nobody reads.
Phase 4: Adapt. Turn Learning into Direction
Adopt is the bridge between Explore cycles. It asks just one wellstructured question: based on what we have just learned, what should we do differently? The greatest risk when adopting agile methodology is that teams don’t do retrospective and release reviews, so the phases lack the institutional learning they are supposed to deliver.
Adopt happens at three levels: at a sprint level, the team knows what processes to change immediately, in a way that is faster than a governance review, and less formal than a change request; at a release level, the team and stakeholders reprioritize the backlog and restructure the next cluster of work by asking: is the overall direction right; do priorities need to shift; should the release date change; and at a portfolio level, the program reviews the distribution of resources across all active projects and rebalancing the portfolio where necessary. This type of collective visibility cannot be achieved by a standalone sprint board, since it displays only one team’s view of the entire portfolio.
Phase 5: Close. End the Project and Capture the Knowledge
Most teams flub the Close. It’s where the sprint completes and the work ships, and the team prepares for another go. Good Close captures formal client acceptance against the conditions of satisfaction (and final billing), financial reconciliation of actual versus planned cost and margin, lessons learned stored where they can be retrieved to inform other teams, and team recognition before the next engagement begins. Of the five project management principles for increasing success in an agile environment, it is the one that an IT services PMO most frequently shortchanges under delivery pressure.
In PMI’s 2018 Pulse of the Profession survey, a substantial percentage of every project dollar is wasted because of poor performance. Much of that sits on the hard drives of project teams, because the Close phase didn’t capture what happened the first time.
How Do the Agile Phases Connect to Scrum and Kanban?
The five phases of project management provide the main framework. The two practices, Scrum and Kanban, shape the micro rhythm within each phase. In Scrum, each sprint is a single Explore cycle, with the retrospective as the Adapt moment.
A project with ten two-week sprints runs through Explore and Adapt ten times, then closes.
Kanban teams run continuous Explore cycles, with Adapt driven by metrics: cycle time, throughput, WIP utilisation rather than by sprint boundaries.
Most IT services organisations run a hybrid: programme-level phases and milestones, teams using Scrum or Kanban, traditional milestone-based billing and governance, especially on fixed-fee or milestone-billed customer contracts. This is where project management’s agile phases come into their own at enterprise level, not within a single sprint team, and it’s just where an agile project management tool has to manage the two worlds.
Agile Phases vs. Traditional Waterfall Phases
Waterfall phases believe everything is discovered early. Agile phases believe the opposite. For an IT services company, a great model is a waterfall, gated approach to billing and compliance checkpoints and governance signoffs, combined with agile phases for delivery.
How Kytes Supports Every Agile Phase for IT Services Teams
The point of breakdown in our experience with IT services businesses that delivery teams work multi-region, multi-client projects is at the intersection of delivery and finance. Kytes is an agentic AI-enabled PSA and agile project management software platform that bridges this gap through every single one of the agile phases of project management. When the sprints finish, the Kytes invoices start.
Envision – Kytes connects project initiation to the proposal and estimation workflow. The initial scope, budget, and conditions of satisfaction are captured in the same platform that will track delivery. The financial baseline is set at Envision, not reconstructed from memory later.
Speculate-Kytes agile project planning software is capable of setting up product backlog, configuring sprint structure, and release planning all with the real resource cost rates preloaded. That is the distinction between agile project planning software that ends at the backlog and one that takes you all the way to the bottom line.
Explore-The sprint board, backlog, velocity and daily standups in Kytes are tied to the timesheet system. Once the team member finishes a sprint task, an approved timesheet will update cost position and billable inventory automatically.
Adapt-The PMO dashboard highlights the sprint health, resource utilization, billing position, and margin position of all live projects on a single screen. When Adapt indicates margin erosion, it identifies precisely where it began.
Close-Upon the close of a project in Kytes, the complete project history is known: plan vs actual cost, plan vs actual margin, timing of billings. This information drives the next comparable estimate for the project.
Frequently Asked Questions
