[2025] Agile Project Management Fundamentals

In this section we will go over agile project management and the processes by which projects can be managed and implemented in small chunks of work. 

 Agile projects are managed in five stages, when combined the are called the Agile Life Cycle. The stages are Envision, Speculate, Explore, Adapt, and Close. In this section we take a look at the highlights of each of these stages. 

The envision phase is the first of 5 phases in the agile life cycle, and provides the foundation for the project. In this section we will go over the envision stage, and how it enables us produce the project charter.

The speculate phase allows the business and technical teams to identify the features in a iteration. In this section we will give you the tools to be successful in this process

We now get to produce the product! Fortunately, with Agile, it doesn't take very long to go from the Envision and Speculate phases to the Explore phase. This phase is all about collaboration between the business and technical team members. We will go over the explorer phase and how its  at the heart of this and show how its at the heart of the agile project. 

 The adapt phase occurs at the end of each sprint immediately following the explore phase. In each adapt phase, you will review with the team what has been delivered compared to what was planned for this sprint, discuss what is and is not working, and agree to any changes that will be applied.

One of the most important success factors for agile is the selection of the right project for you to apply agile methods. In this section we will go over the three characteristics that make a project a good agile project candidates.

In the project charter we describe the customer's visions of the final product and overall boundaries for the project. We follow it up with with the creation of the Product Data Sheet or PDS. This is a great planning document and provides an executive summary of the project. 

 Most sprint durations are from 2  to 12 weeks. This duration includes the speculate, explore, and adapt phases. Determining the length of your sprints and the number of features you'll try to build during each sprint is called the sprint structure. You'll want to create a sprint structure that is appropriate for your specific project. In this section we will discuss some hints and tips to determine your sprint structure.

 As with traditional projects, risks should be assigned and assessed against specific tasks in your plan or specific features in the agile environment. In a agile project, the other way to manage risk is through the features you assign to each sprint.  In this section we will go over how to mitigate and manage risk.

The explore phase of the agile project life cycle is different from non-agile build life cycle phases. Your role as a project manager is to observe and guide versus lead. You actually take a back seat to the process and you lead via coaching.

During the build stage, effective collaboration is essential for the sprint to be successful. As project manager, you can do a lot to support the team during this phrase, and ensure collaboration is working as desired. The plan, do, check, adjust, or PDCA cycle is a great technique to foster collaborative behavior.

Agile projects expect and are designed to accommodate change. Being able to identify and document requirements throughout an agile project based on current business need is a key ingredient to any agile project. During the speculate phase, we discussed the use of index cards to document features. Now we'll discuss approaches and techniques to document the features and requirements. A great technique is to have a business analyst work ahead of the agile development team by one or two sprints.

Many people who don't understand Agile believe Agile Projects do not have control mechanisms. That's actually far from the truth. There are Agile-specific techniques that help you manage and monitor your Agile Projects. Scope is managed by the backlog list. Scope is controlled by completing features to reduce the backlog list, and adding new features as they are identified. The business in conjunction with the technical team consistently prioritizes to determine which features will be implemented during the next sprint.

The daily stand-up meetings are the heartbeat of an Agile project. This meeting is crucial to the success of the project, as critical information should be shared to enable roadblocks to be removed. The stand-up meetings should be about 15 minutes long, sharp, and to the point. Having the attendees remain standing helps keep the meeting short, upbeat, and active. All business and technical specialist team members should attend along with the project manager, sometimes called the ScrumMaster. Ideally, the project manager does not lead the meeting. Instead, team members will each provide their update. Have your team present their status in a different sequence each day. Having them rotate who goes first adds energy to your meetings.

One of the best characteristics of agile project management, is the opportunity to obtain feedback frequently and apply changes based on what the team has learned. The key is asking the right questions, and using your project control tools, to ensure the project is being reviewed with a critical eye. In the adapt and close phase, we discuss the things that need to occur during the adapt phase. Here we will discuss some of the techniques available to obtain solid feedback. The first trick, is to not wait until the adapt phase to get feedback. In the team room, have an area where team members can jot down lessons learned at any time. Insure the information is complete, so you have the context. Keep in mind, you don't need to know how you're going to resolve the issue. Just get the feedback written down. Sample items include, it's taking longer to complete medium sized features than planned. Daily stand up meetings are taking more than 15 minutes.

We know Agile is all about the business and adapting to their current needs as we cycle through each sprint. However, there are things to consider when adapting to business changes. Let's assume you have 100 features, and they have been prioritized by the business, and you're planning to implement them over five sprints. From a technical perspective, it might make sense to group the features differently between the sprints.

While we recognize that there are allot of creative, non-repetitive, variable work in agile development projects, many work items, ceremonies, and activities can benefit from systematic, reproducible and standardized tasks test and options that can be captured in customizable checklists prepared and used by empowered agile teams.