🏗️ PMP: What a PM Should Do, Be, Think & Avoid

🎯 What a PM Is — The Foundation

A Project Manager (PM) is NOT just a task tracker. A PM is the integrator, servant leader, communicator, and value deliverer who connects strategy to execution.

🧭 PM Mindset & How to Think

✅ What PM Should DO — Core List (Part 1)

Planning & Initiation

• Define and document the Project Charter before starting any detailed planning.
• Identify all stakeholders early — do not wait until mid-project.
• Develop the Project Management Plan collaboratively with the team.
• Define the scope clearly and get it approved before executing.
• Establish a realistic schedule baseline with team input — never create the schedule alone.
• Identify constraints, assumptions, and dependencies from day one.
• Get formal sponsor sign-off on the Project Charter and Management Plan.
• Conduct a proper kickoff meeting to align all stakeholders.
• Decompose work into a WBS to ensure nothing is missed.
• Define acceptance criteria with the customer before work begins.

Execution & Monitoring

• Monitor and control project performance against the baselines continuously.
• Use Earned Value Management (EVM) to assess schedule and cost performance.
• Conduct regular status meetings with a clear agenda.
• Update the issue log promptly when problems arise.
• Report project status accurately and transparently — even when news is bad.
• Implement change control rigorously — no unauthorized scope changes.
• Document lessons learned throughout, not just at project close.
• Validate deliverables with the customer using Validate Scope process.
• Perform Integrated Change Control through the CCB.
• Track risks continuously and implement responses as needed.

✅ What PM Should DO — Core List (Part 2)

Project Closure

• Obtain formal final acceptance from the customer before closing.
• Archive all project documents in an organized manner.
• Conduct a formal lessons learned meeting with the whole team.
• Release team members formally and recognize their contributions.
• Close all contracts and confirm final payments with vendors.
• Update the organizational process assets (OPA) with project records.
• Transition deliverables to operations with proper documentation.
• Prepare and submit a final project report to the sponsor.

✅ Stakeholder DO's

• Identify ALL stakeholders — internal, external, positive, and negative.
• Analyze each stakeholder's power, interest, and influence.
• Create and maintain a Stakeholder Engagement Plan.
• Tailor communication to each stakeholder's needs, style, and culture.
• Engage resistant stakeholders early — understand their concerns.
• Keep stakeholders at the desired engagement level throughout the project.
• Escalate unresolved stakeholder conflicts to the sponsor if needed.
• Manage stakeholder expectations proactively — set realistic expectations early.
• Re-assess stakeholder list when project conditions change significantly.

✅ Team Leadership DO's

• Act as a servant leader — remove obstacles, not assign blame.
• Trust the team — delegate appropriately and avoid micromanaging.
• Recognize and celebrate team achievements, big and small.
• Create a psychologically safe environment — encourage honest communication.
• Resolve team conflicts quickly and constructively using conflict resolution best practices.
• Use motivational theory to understand what drives each team member.
• Hold team members accountable while supporting them with resources and coaching.
• Conduct regular one-on-ones to check in on performance and well-being.
• Foster a culture of continuous improvement within the team.
• Adapt your leadership style to the situation and team maturity level.

✅ Risk & Issues DO's

• Identify risks early in planning — before issues occur.
• Involve the team in risk identification — they know what can go wrong.
• Perform both qualitative and quantitative risk analysis.
• Develop risk responses for every significant risk (avoid, mitigate, transfer, accept).
• Assign a risk owner to every identified risk.
• Maintain and update the Risk Register throughout the project.
• Distinguish between a risk (uncertain future) and an issue (current problem).
• Track residual risks and monitor secondary risks from responses.
• Maintain a management reserve and contingency reserve for uncertainty.

✅ Communication DO's

• Spend approximately 90% of your time communicating (PMI guideline).
• Develop a Communications Management Plan early.
• Use the communication model: verify the message was understood, not just received.
• Choose the right communication channel for the message (formal vs informal, written vs verbal).
• Listen actively — ask clarifying questions and summarize what was said.
• Document important decisions in writing — verbal-only decisions lead to disputes.
• Use push, pull, and interactive communication appropriately.
• Be transparent — report both good and bad news promptly.
• Use the formula n(n-1)/2 to count communication channels.

✅ Agile / Hybrid DO's

• Promote self-organizing teams — the team decides how, not the PM.
• Facilitate Sprint Planning, Daily Standups, Sprint Reviews, and Retrospectives.
• Prioritize the Product Backlog based on business value with the Product Owner.
• Eliminate impediments quickly — your job is to clear the path.
• Inspect and adapt at every opportunity — embrace change as a competitive advantage.
• Track progress using burndown charts and velocity.
• Select the right approach (predictive, agile, or hybrid) based on project needs.
• Use Definition of Done (DoD) to ensure quality is built in.
• Deliver working increments frequently — demonstrate value early and often.

🌟 What PM Should BE — Character & Traits

🌟 Leadership Style — What Works When

🌟 Ethical Standards — What PM Must BE

🚫 What PM Should NOT DO — Critical Don'ts

• Do NOT create the project schedule alone without team input — it will be unrealistic and unmotivating.
• Do NOT approve scope changes informally — always go through change control.
• Do NOT gold-plate — adding features not in the scope baseline without approval wastes budget and time.
• Do NOT hide bad news — report problems early. A delay reported late is always worse.
• Do NOT blame the team publicly — address performance issues in private, professionally.
• Do NOT skip lessons learned until the end — capture them throughout the project.
• Do NOT ignore a resistant or negative stakeholder — engage them directly and proactively.
• Do NOT allow scope creep silently — every new request must be evaluated through change control.
• Do NOT manage risks reactively — identify and plan responses before issues occur.
• Do NOT micromanage — trust the team, delegate, and focus on the big picture.
• Do NOT make decisions in isolation on major issues — involve the right stakeholders.
• Do NOT let conflicts fester — address them early using collaborative problem-solving first.
• Do NOT skip the project charter or contract review at project start.
• Do NOT assume verbal agreements are enough — always document key decisions in writing.
• Do NOT violate the PMI Code of Ethics — even under pressure from management or client.

🚫 People & Team Don'ts

• Do NOT play favorites — apply policies consistently to all team members.
• Do NOT take credit for team achievements — celebrate the team publicly.
• Do NOT avoid difficult conversations — they only get harder with time.
• Do NOT use formal authority as your first tool — use influence, not power.
• Do NOT ignore team morale issues — low morale equals low productivity.
• Do NOT assign blame when problems arise — focus on solutions and improvement.
• Do NOT allow bullying or harassment — it violates PMI's Code of Ethics and harms everyone.
• Do NOT overload high performers because they're reliable — prevent burnout.
• Do NOT fail to recognize personal and cultural differences in your global team.

🚫 Process Don'ts

• Do NOT skip risk planning because the project seems low-risk — every project has risks.
• Do NOT close a project without formal sign-off from the customer or sponsor.
• Do NOT use management reserve without proper authorization — it is not in your control.
• Do NOT skip quality planning — quality assurance prevents defects; quality control detects them.
• Do NOT allow the critical path to slip without evaluating impact and communicating to stakeholders.
• Do NOT try to fix a major issue alone — escalate when needed, quickly.
• Do NOT confuse outputs with outcomes — delivering a system is not the same as achieving business value.
• Do NOT forget to update the OPA and EEF at project close.

💡 How PM Should Think — Thinking Modes

💡 Decision Frameworks

💡 Conflict & Crisis Thinking

Conflict Resolution Order (PMI Preference)

1. Collaborate / Problem-Solve — Best: all parties work toward a win-win solution (most preferred)
2. Compromise / Reconcile — Both parties give something up; both partially win
3. Smooth / Accommodate — Emphasize agreement; downplay differences (temporary)
4. Force / Direct — PM uses authority to impose a solution (damages relationships)
5. Withdraw / Avoid — Postpone or retreat; problem remains (least preferred)

📝 Master Cheat Sheet Table

🏆 PMP Exam Tips & Common Traps

🔑 Key Vocabulary — Click for Definitions

📐 Exam Scenarios & Best Answers