PMP

Manage conflict

• Manage conflictConflict is a normal part of any project that brings people with different priorities together, not a failure to hide. The five classic conflict-resolution techniques, and when each one actually fits.2 min read

Lead a team

• Lead a teamThe different leadership styles a project manager might need depending on the situation, and PMP's gradual shift toward favoring empowering styles over traditional command-and-control leadership.2 min read

Support team performance

• Support team performanceTeam performance isn't assessed only at project end — continuous feedback and addressing a performance dip early prevent a big surprise near closure.1 min read

Empower team members and stakeholders

• Empower team members and stakeholdersDelegating decisions to the most appropriate level, not always the highest one — and why micromanagement weakens team performance instead of improving it, even with good intentions from the leader.1 min read

Ensure team members/stakeholders are adequately trained

• Ensure team members/stakeholders are adequately trainedTraining isn't a one-off box-ticking activity — it starts by identifying an actual skill gap threatening project execution, and ends by verifying its real effect, not just recording attendance.1 min read

Build a team

• Build a teamThe five stages of team development in Tuckman's model, from cautious forming to mature performing, and how the leader's role changes at each stage.1 min read

Address and remove impediments, obstacles, and blockers for the team

• Address and remove impediments for the teamThe project manager's role in removing impediments isn't personally solving every problem, but facilitating the team's own resolution when it can, and escalating quickly when it can't.2 min read

Negotiate project agreements

• Negotiate project agreementsBest Alternative to a Negotiated Agreement (BATNA) — knowing what you'll do if negotiation fails is your strongest bargaining chip — and the difference between distributive (one side wins) and integrative (both sides win) negotiation.1 min read

Collaborate with stakeholders

• Collaborate with stakeholdersNot every stakeholder needs the same level of engagement — the Power/Interest Grid as a tool for determining who needs intensive communication and who just needs to be kept informed.1 min read

Build shared understanding

• Build shared understandingCommunication doesn't guarantee understanding — everyone can receive the same message and understand it in completely different ways. Building shared understanding means actively verifying everyone means the same thing, not assuming it.1 min read

Engage and support virtual teams

• Engage and support virtual teamsA virtual team needs more communication structure, not less — asynchronous documentation, deliberate outreach, and conscious extra effort to prevent an isolation that doesn't surface as automatically as in a co-located team.1 min read

Define team ground rules

• Establish team ground rulesTeam ground rules work best when the team itself helps craft them — real buy-in, not externally imposed rules — and they need periodic review, not permanent fixity.1 min read

Mentor relevant stakeholders

• Mentor relevant stakeholdersMentoring is a long-term relationship that builds the other party's ability to act independently in the future — not just answering a question or giving a one-time instruction.1 min read

Promote team performance through the application of emotional intelligence

• Promote team performance through emotional intelligenceEmotional intelligence isn't suppressing emotions but managing the response to them — self-awareness, self-regulation, and empathy are practical project manager tools, not just personality traits.1 min read

Execute project with the urgency required to deliver business value

• Execute project with the urgency required to deliver business valueThe required urgency means matching the pace of work to the actual value-realization window — not reckless acceleration that sacrifices quality, nor unnecessary slowness that misses value that could have been delivered sooner.1 min read

Manage communications

• Manage communicationsThree core communication methods — interactive, push, and pull — each with its own fit, and push specifically guarantees only sending, not actual understanding.1 min read

Assess and manage risks

• Assess and manage risksThe risk register, the five response strategies for threats and their opportunity counterparts, and the distinction most candidates confuse: contingency reserve vs. management reserve.3 min read

Engage stakeholders

• Engage stakeholdersThe stakeholder engagement assessment matrix compares each stakeholder's current level to their desired one — from Unaware to Leading — directing effort toward real gaps, not everyone equally.1 min read

Plan and manage budget and resources

• Plan and manage budget and resourcesResource leveling vs. resource smoothing — two conflict-resolution tools that look similar but one can extend the critical path while the other can't — and the three most common estimating techniques.2 min read

Plan and manage schedule

• Plan and manage scheduleTotal float vs. free float — the distinction most candidates confuse right after grasping the critical path itself — and three-point (PERT) estimating as a tool to reduce individual estimation bias.2 min read

Plan and manage quality of products/deliverables

• Plan and manage quality of products/deliverablesQuality assurance focuses on the process and preventing defects beforehand; quality control focuses on the actual deliverable and detecting defects after the fact — a common confusion despite the core difference between the two.1 min read

Plan and manage scope

• Plan and manage scopeScope creep vs. gold plating — two unplanned scope additions that look similar but come from entirely different sources — and the requirements traceability matrix as a linking tool.2 min read

Integrate project planning activities

• Integrate project planning activitiesThe project management plan isn't just the subsidiary plans (scope, schedule, cost, quality...) stapled together side by side — it's integrating them into one consistent document, where every decision in one subsidiary plan aligns with the decisions in the rest.1 min read

Manage project changes

• Manage project changesEvery change — however small or beneficial it seems — goes through one unified formal control process before implementation; bypassing that process is the very definition of scope creep.1 min read

Plan and manage procurement

• Plan and manage procurementWho bears the risk of cost overrun in each contract type? Fixed price, cost-reimbursable, and time & materials — three contract types that distribute risk between buyer and seller in radically different ways.1 min read

Manage project artifacts

• Manage project artifactsProject artifacts (plans, registers, baselines) aren't documents written once and forgotten — managing them means keeping them current, accurate, and accessible throughout the project life cycle.1 min read

Determine appropriate project methodology/methods and practices

• Determine appropriate project methodology/methods and practicesPredictive vs. adaptive vs. hybrid — not choosing "agile because it's modern", but a decision grounded in requirements clarity and their expected rate of change.1 min read

Establish project governance structure

• Establish project governance structureProject governance defines who has the authority to make which decision and when something gets escalated to whom — a clear authority framework that prevents ambiguity about who decides what, not an extra bureaucratic layer.1 min read

Manage project issues

• Manage project issuesA risk is a future possibility, an issue is a present reality needing immediate handling — and when a negative risk materializes, it effectively becomes an issue needing its own logging and follow-up.1 min read

Ensure knowledge transfer for project continuity

• Ensure knowledge transfer for project continuityKnowledge confined to a single person is a real risk to project continuity — proactive knowledge transfer (documentation, cross-training) protects the project from suddenly losing critical knowledge.1 min read

Plan and manage project/phase closure

• Plan and manage project/phase closureClosure happens whether a project completes successfully or is terminated early — formal acceptance, documenting lessons learned, and releasing resources are necessary steps either way, not a reward reserved for success.1 min read

Plan and manage project compliance

• Plan and manage project complianceCompliance comes from more sources than just the law — the four main categories, and why non-compliance risks deserve higher-priority handling than ordinary project risks.1 min read

Evaluate and deliver project benefits and value

• Evaluate and deliver project benefits and valueFinishing a project on time and on budget doesn't automatically mean it delivered the intended business value. How actual benefit is measured, and who stays accountable for it after the project closes.2 min read

Evaluate and address external business environment changes for impact on scope

• Evaluate and address external business environment changesA project doesn't operate in a vacuum — a new law, a competitor's launch, or an economic shift can force a scope change nobody inside the team requested. Scanning the external environment as an ongoing responsibility, not a one-time event.2 min read

Support organizational change

• Support organizational changeDelivering an excellent technical output doesn't mean the organization will actually adopt it. The difference between project management and organizational change management, and why resistance to change is a normal, expected reaction, not an unjustified obstacle.1 min read