Tasks 9–10: Evaluate project status; manage project closure

Welcome to Task 9: Evaluate Project Status

Hello there, future PMP! Have you ever started a long road trip and checked your GPS every hour to make sure you were still on the right path and would arrive on time? That is exactly what Task 9: Evaluate Project Status is all about. In the world of project management, we don't just "hope" things are going well; we use specific tools and measurements to prove it.

In this chapter, we will learn how to measure where the project stands compared to where we planned to be. This is a vital part of Domain II: Process because it ensures the project stays on track to deliver value to the organization.

1. Choosing the Right Yardstick: Methods and Metrics

Before you can measure status, you need to decide what and how you are going to measure. You can't measure the "success" of a software project the same way you measure a construction project.

Work Performance Data, Information, and Reports
Don't worry if these terms sound similar. Think of them as a "data evolution" process:
• Work Performance Data: These are the raw facts. Example: "We spent $5,000 today."
• Work Performance Information: This is the data compared to the plan. Example: "We spent $5,000, but we were only supposed to spend $4,000. We are over budget."
• Work Performance Reports: This is the final summary for stakeholders. Example: A status dashboard showing a red light for the budget.

Key Metrics to Track

Common metrics include Schedule (Are we late?), Cost (Are we over budget?), Scope (Are we doing the right work?), and Quality (Is the work good?).

Key Takeaway: You must determine your metrics early so everyone knows what "success" looks like.

2. The "Gold Standard": Earned Value Management (EVM)

EVM is often the part students find most intimidating, but it’s actually very logical! It’s just a way to combine scope, schedule, and cost to see how the project is doing.

Imagine you are hired to paint 10 rooms for $1,000 ($100 per room) in 10 days.
• Planned Value (PV): What you expected to have done. If it's Day 5, your PV is $500 (5 rooms).
• Earned Value (EV): The value of the work you actually finished. If you only finished 3 rooms, your EV is $300.
• Actual Cost (AC): What you actually spent. If you spent $400 to paint those 3 rooms, your AC is $400.

Performance Formulas

We use variances (subtraction) and indices (division) to see how we are doing:
• Schedule Variance (SV): \( SV = EV - PV \). If it's negative, you are behind schedule!
• Cost Variance (CV): \( CV = EV - AC \). If it's negative, you are over budget!
• Schedule Performance Index (SPI): \( SPI = \frac{EV}{PV} \).
• Cost Performance Index (CPI): \( CPI = \frac{EV}{AC} \).

A Simple Trick for Indices (SPI and CPI)

Think of the number 1.0 as your target.
• Over 1.0 = You are a superstar! (Under budget or ahead of schedule).
• Under 1.0 = You have a problem! (Over budget or behind schedule).
• Exactly 1.0 = You are exactly on plan.

Quick Memory Aid: "I over P" (Index = EV / something). For CPI, divide by Cost (AC). For SPI, divide by Planned (PV).

3. Evaluating Project Health (Beyond Just Math)

While the numbers (EVM) are important, evaluating status involves looking at the whole picture.

Variance Analysis: This is the "Why?" When you see a variance, you need to investigate. Is the schedule behind because of a one-time storm, or is the team working slower than expected?
Trend Analysis: This looks at performance over time. Are we getting better or worse? If your CPI has been dropping for three months, you have a growing problem.
Reviewing Quality and Risks: Status isn't just about money. Are we meeting the quality standards? Are new risks popping up that could ruin the project next week?

Key Takeaway: Evaluating status is about looking at the past (Actuals), the present (Variances), and the future (Trends and Risks).

4. Communicating Status to Stakeholders

Once you know the status, you have to tell people. But be careful—different people need different levels of detail.

• The Sponsor: Usually wants a high-level "Stoplight Report" (Green, Yellow, Red).
• The Team: Needs the gritty details to fix specific issues.
• The Customer: Wants to know if their deadline will be met.

Common Pitfall: The "Watermelon" Project

Don't fall into the trap of "Watermelon Reporting"—where the project looks Green on the outside (in your reports) but is actually Red on the inside (full of problems). Be honest about your status so stakeholders can help you fix issues before it's too late!

Quick Review Box

• PV: What we planned to do.
• EV: What we actually finished (expressed in dollars).
• AC: What we actually spent.
• CPI/SPI > 1.0: Good!
• CPI/SPI < 1.0: Bad!
• Communication: Tailor the status report to the specific audience.

Don't Worry if it Seems Tricky!

Evaluating project status is a skill that gets easier with practice. If you find the EVM formulas confusing, just remember: EV always comes first in the formula. Whether you are subtracting or dividing, start with Earned Value. You've got this!

Welcome to the Finish Line: Task 10 - Manage Project Closure

Hello, future PMP! You have worked hard to plan, execute, and monitor your project. Now, it is time for the final step: Project Closure. Many students think closure is just about "finishing the work," but in the PMP world, it is a formal process. Think of it like moving out of a rental apartment—you don't just leave the keys and walk away; you have to clean up, settle the bills, get your deposit back, and hand over the keys formally. In this chapter, we will learn how to wrap things up so that the organization can move on and learn from your success!

1. Why Do We Close a Project?

Closure is not just for projects that are successful. You must perform closure for completed projects, cancelled projects, and at the end of every phase in a large project. We do this to ensure that all the "loose ends" are tied up and that the organization doesn't keep spending money on something that should be over.

Key Objectives of Closure:

- Verify that the project work is complete.
- Formally hand over the product to the customer or operations team.
- Gather lessons learned so the company gets smarter.
- Release the team so they can go help on other projects.
- Archive records for legal or historical reasons.

2. The Steps to a Successful Closure

Don't worry if this seems like a lot of paperwork at first. Just follow these steps in order, and you will be a closure pro!

Step A: Confirm Completion Criteria

How do we know we are actually "done"? We look at the Project Management Plan and the Scope Baseline. You must ensure that every requirement has been met and that the customer has formally signed off on the deliverables.

Analogy: If you hire a painter to paint your house, "done" isn't when they put the brush down. "Done" is when you walk around the house together, agree it looks great, and sign the invoice.

Step B: Transfer of Ownership

Once the product is finished, you need to hand it over to the people who will actually use it. This is called Transfer of Ownership or Transition. This might involve training the new users or handing over manuals and warranties.

Quick Tip: If you are building a software app, closure involves moving it from the "testing environment" to the "live environment" where real customers can use it.

Step C: Administrative Closure

This is the "paperwork" phase. It is very important for the PMP exam! You must:
- Close out any contracts with vendors.
- Settle all financial accounts (make sure all bills are paid and the project budget is closed).
- Complete a Final Project Report that summarizes how the project went (was it on time? was it on budget?).
- Archive all project documents in the Organizational Process Assets (OPAs).

Step D: Lessons Learned and Knowledge Transfer

This is arguably the most valuable part of closure for your company. You sit down with the team and discuss: "What went well?" and "What went wrong?"
- Did you know? PMP emphasizes that Lessons Learned should be collected throughout the project, but they are finalized during closure. These become part of the company's "library" to help future Project Managers avoid the same mistakes.

Step E: Release the Team

Once the work is done and the paperwork is filed, it is time to release your team members. In a Matrix Organization, this means they go back to their functional managers. In a Project-Oriented Organization, they might be assigned to a brand new project.

Key Takeaway: Administrative closure is mandatory even if a project is terminated early! You still need to document why it failed and archive what was finished.

3. Memory Aid: The "C.L.O.S.E." Mnemonic

To help you remember the main activities of Task 10, just remember the word C.L.O.S.E.:

C - Confirm work is done and accepted.
L - Lessons learned are documented.
O - Ownership is transferred to the customer.
S - Settle all financial and legal obligations.
E - Exit and release the team.

4. Common Pitfalls to Avoid

On the PMP exam, watch out for these "trick" scenarios:

- Mistake: Releasing the team before the lessons learned are finished. (The team is the source of the lessons! Keep them until the session is over.)
- Mistake: Thinking closure isn't necessary for a project that was cancelled. (You still have to pay the bills and document why it was cancelled!)
- Mistake: Waiting until the very end of a 2-year project to start thinking about closure. (Closing should happen at the end of every phase.)

5. Tools and Techniques for Closure

How do we actually get closure done? We use these simple tools:

1. Expert Judgment

Consult with legal experts, procurement offices, or senior managers to ensure you haven't missed any technical or legal requirements.

2. Meetings

The "Lessons Learned" meeting or the "Post-Mortem" meeting is where the magic happens. It should be an open, honest environment where the team can speak freely.

3. Document Analysis

Reviewing the project management plan and logs to make sure everything was checked off. If it’s not in the documents, as far as the PMP exam is concerned, it didn’t happen!

Quick Review Box:
- Final Product: Handed to the customer.
- Final Report: Summarizes project performance.
- Lessons Learned: Added to the organization's library (OPAs).
- Team: Released to their next adventure.

Summary: Task 10 Wrap-Up

Closing a project is more than just saying "goodbye." It is a structured process of verifying scope, transferring the product, archiving records, and celebrating the team’s hard work. By following these steps, you ensure the project's success is recognized and the organization is better prepared for the next challenge. Now you are ready to move on to the next task in Domain II!