Saturday, 1 February 2025

Important PMP Terms

 

1. Introduction to PMP Exam Key Terms

  • These terms often appear as drag-and-drop or multiple-choice questions on the PMP exam.
  • Understanding them helps with project planning, execution, and team management.
  • Example:
    • If a team procrastinates until the deadline, they are showing Student Syndrome.

2. Key Terms & Definitions

1) Student Syndrome (Planned Procrastination)

  • Definition: People delay starting a task until the last possible moment, eliminating any buffer time.
  • Impact: Increases risk, stress, and errors due to last-minute rush.
  • Example:
    • A developer is given five days to complete a module but starts only on the last day, leaving no time for fixes if issues arise.
  • Solution: Encourage early starts and incremental progress tracking.

2) Parkinson’s Law

  • Definition: Work expands to fill the time allocated for its completion.
  • Impact: Leads to inefficiency and wasted time.
  • Example:
    • A tester is given two weeks to finish testing but stretches the work to fit the full two weeks, even though it could be done in one.
  • Solution: Set realistic deadlines and use timeboxing techniques.

3) Self-Protection

  • Definition: People act in ways that avoid risk or harm to themselves in the present or future.
  • Impact: Leads to cautious behavior, delayed decisions, and lack of initiative.
  • Example:
    • A team member avoids reporting risks because they fear blame if something goes wrong.
  • Solution: Create a safe environment where team members feel comfortable raising concerns.

4) Sandbagging (Underpromise & Overdeliver)

  • Definition: Deliberately setting low expectations so that results seem better than expected.
  • Impact: Creates false expectations and inefficiencies in project planning.
  • Example:
    • A development team knows they can complete six features but only commits to four to look good when they deliver six.
  • Solution: Encourage accurate estimates rather than manipulating expectations.

5) Dropped Baton (Poor Handover Between Teams)

  • Definition: When one team completes their task but the next team isn’t ready to take over, causing delays.
  • Impact: Wasted time, resource inefficiency, and missed deadlines.
  • Example:
    • The development team finishes coding early, but the testing team isn’t ready, delaying the project by a week.
  • Solution: Improve handover coordination and ensure teams are ready for transitions.

3. Why These Terms Matter for PMP Exam & Real Projects

  • Helps recognize inefficiencies in project execution.
  • Improves time and resource management.
  • Enhances teamwork and coordination.
  • Prepares you for exam questions related to project behaviors and risks.

Key Takeaway: Recognizing These Behaviors Leads to Better Project Management

  • Avoid procrastination & inefficiencies (Student Syndrome & Parkinson’s Law).
  • Encourage transparency & realistic commitments (Self-Protection & Sandbagging).
  • Ensure smooth handovers between teams (Dropped Baton).

No comments:

Post a Comment