Procurement, Leadership & Agile

🤝 Procurement, Leadership & Agile

Study Notes — Page 7  |  ClearPMPExam.com

Contract Types Tuckman’s Model Conflict Resolution Motivation Theories Agile Values Scrum Roles

Part A — Procurement Management

Definition

Procurement Management covers obtaining goods, services, or results from outside the project team — managing vendors, contracts, and external relationships to ensure deliverables meet project needs.

Whenever you hire an external vendor, agency, or contractor — that is procurement. The PM’s job is to select the right contract type, manage the vendor relationship, and ensure what is delivered matches what was agreed.


1. Contract Types — The Most Tested Procurement Topic

There are three contract types. The exam tests them constantly — usually by describing a project scenario and asking which contract type is most appropriate, or which party bears the most risk.

Type 1 — Fixed Price
🔒

Fixed Price (FP / FFP)

Agreed price upfront. Seller delivers for that price — no matter what it actually costs them.

Use when: Scope is clear, well-defined, and unlikely to change.

Real example: “Build this website for ₹10 lakh.” If it costs the vendor ₹12 lakh to build — their problem, not yours.

Seller bears the risk
Type 2 — Time & Material
⏱️

Time & Material (T&M)

Pay for actual time worked plus materials used. No fixed total price.

Use when: Scope is not fully defined, or for smaller pieces of work. Often used as a starting contract while scope is clarified.

Real example: “₹500/hour + cost of materials.” Total cost depends on how long it takes.

Shared risk
Type 3 — Cost Plus
📈

Cost Plus (CPFF / CPIF)

Buyer reimburses all actual costs plus pays an additional fee. No cost ceiling for the buyer.

Use when: Scope is highly uncertain, complex, or R&D-based. The buyer accepts the financial risk because the work is unpredictable.

Real example: Drug research contract — reimburse all lab costs + pay a fixed fee. Total cost is unknown upfront.

Buyer bears the risk

Risk Spectrum — Who Bears More Risk?

Buyer has LEAST risk Buyer has MOST risk
Fixed Price
Seller takes risk
Time & Material
Shared
Cost Plus
Buyer takes risk
📌 EXAM TIP — Contract Trigger Words

“Well-defined scope / fixed budget” → Fixed Price. “Unclear scope / hourly rate” → T&M. “Research / highly uncertain / reimburse costs” → Cost Plus. “Most risk for seller” → Fixed Price. “Most risk for buyer” → Cost Plus.

🏥 Real Example — Pharma Agency Contracts

Fixed Price: “Design and deliver 10 HCP education brochures for ₹2 lakh.” Scope is clear. Agency bears any cost overrun.

T&M: “Provide a medical writer at ₹3,000/hour as needed.” Useful when you don’t know exactly how many hours you’ll need.

Cost Plus: “Conduct clinical literature review — we’ll pay all research costs plus a 15% management fee.” Scope is uncertain, so buyer pays whatever it takes.


Part B — Leadership & Team Management


2. Tuckman’s Team Development Model — The 5 Stages

Every project team goes through five stages of development. The PM’s role changes at each stage. The exam gives you a scenario describing what the team is doing and asks which stage they are in — or what the PM should do.

1
Forming

Team meets. Polite. Roles unclear. Everyone figuring out where they stand.

PM: Direct & Guide
2
Storming

Conflicts emerge. Disagreements. Power struggles. Most difficult stage.

PM: Coach & Resolve
3
Norming

Team settles. Rules established. Trust builds. Roles become clear.

PM: Support
4
Performing

High productivity. Self-directed. Team works well together without micromanagement.

PM: Delegate
5
Adjourning

Project ends. Team disperses. Members move to other assignments.

PM: Celebrate & Release
📌 EXAM TIP — Storming is Most Tested

Most conflict-related exam questions happen in Storming. When the question describes team disagreements or interpersonal friction — think Storming. The best PM response at this stage is always to coach and facilitate — never to force a resolution or ignore it.

🧠 Memory Trick — 5 Stages in Order

“Forming → Storming → Norming → Performing → Adjourning”  =  “Friendly Students Never Perform Alone”


3. Conflict Resolution — Ranked Best to Worst

The PMP exam has a clear preference order for how conflicts should be handled. In almost every conflict question, the best answer is Collaborate/Problem-Solve — unless the question specifically says there is a crisis or time pressure.

1
⭐ Collaborate / Problem-Solve

Work with both parties to find a win-win solution that satisfies everyone. Best long-term outcome. PMP’s always preferred answer.

2
Compromise / Reconcile

Both parties give up something. No one fully wins. Acceptable when time is short or a full solution isn’t possible. Neither party is fully satisfied.

3
Smooth / Accommodate

Downplay differences and focus on agreements. Temporarily reduces tension but doesn’t resolve the root cause. A short-term fix only.

4
Force / Direct

PM uses authority — one side wins, the other loses. Creates resentment. Only appropriate in a genuine crisis or when a quick decision is needed immediately.

5
Withdraw / Avoid

Ignore the conflict. Walk away. Never resolves anything. The problem persists and usually gets worse. Always the worst choice in PMP.

📌 EXAM TIP — One Exception to the Rule

Collaborate/Problem-Solve is almost always the answer — except when the exam says something like “the team has 30 minutes to make a decision” or “a crisis requires an immediate call.” In those cases, Force/Direct may be the right answer. Otherwise, always default to Collaborate.


4. Leadership vs Management — The Core Difference

🌟 Leadership

👥 Focuses on people — inspiring, motivating, guiding
🎯 Sets vision and direction — where are we going and why
💡 Encourages innovation and taking initiative
🤝 Builds trust and morale — team wants to follow

Example: PM tells the team how this pharma campaign will improve patient lives — inspiring them to go the extra mile.

⚙️ Management

📋 Focuses on processes — planning, organising, controlling
Ensures tasks are completed on time and within budget
📊 Tracks performance against baselines and plans
🔧 Maintains order and compliance with standards

Example: PM assigns tasks, tracks deadlines on the Gantt chart, and reports progress to the sponsor weekly.

Key exam rule: Leadership inspires people to want to achieve goals. Management ensures the right processes are in place to actually achieve them. A great PM does both — but PMP questions increasingly favour servant leadership and people-first approaches.


5. Motivation Theories — Quick Reference

Three motivation theories appear regularly in the exam. Know the key concept and the trigger word for each.

🏔️
Maslow’s Hierarchy of Needs

People are motivated by a pyramid of needs — lower needs must be met before higher ones become motivating. Five levels from bottom to top: Physiological → Safety → Social → Esteem → Self-Actualization.

Exam trigger: “What motivates someone at the top of Maslow’s pyramid?” → Self-actualization (growth, achievement, reaching potential). “Basic needs” → Physiological (food, shelter).

X / Y
McGregor’s Theory X and Theory Y

Theory X: Manager assumes people dislike work, are lazy, and must be closely controlled and micromanaged. Uses punishment and authority. Theory Y: Manager assumes people are self-motivated, enjoy work, and thrive when given autonomy and responsibility.

Exam trigger: “The manager watches every employee closely, assigns tasks strictly, and uses punishments” → Theory X. “The PM trusts the team, gives autonomy, and encourages ownership” → Theory Y. PMP prefers Theory Y.

🌡️
Herzberg’s Two-Factor Theory

Hygiene Factors — if absent, they cause dissatisfaction, but their presence doesn’t motivate. Salary, job security, working conditions, company policies. Motivators — these actually drive satisfaction and performance. Achievement, recognition, interesting work, growth opportunities.

Exam trigger: “Adding more salary won’t motivate — it just prevents dissatisfaction” → Hygiene Factor. “Recognition for achievement motivated the team” → Motivator. Key insight: removing dissatisfaction ≠ creating motivation. You need both.


Part C — Agile & Hybrid

What is Agile?

Agile is an iterative, flexible approach to project delivery where work is done in short cycles (sprints), with continuous feedback and adaptation. It prioritises people, working product, customer collaboration, and responding to change over rigid plans and processes.


6. The 4 Agile Values — The Manifesto

The Agile Manifesto defines four core values. Each value says we prefer the LEFT side MORE than the RIGHT — but both sides have value. This distinction is critically important for the exam.

Individuals & Interactions
MORE than
Processes & Tools
Working Software / Product
MORE than
Comprehensive Documentation
Customer Collaboration
MORE than
Contract Negotiation
Responding to Change
MORE than
Following a Plan
📌 EXAM TIP — Both Sides Have Value

The most common wrong answer is to say “Agile doesn’t care about processes/documentation/contracts/plans.” That is WRONG. Agile values BOTH sides — it just values the left side MORE. If the exam asks “does Agile ignore documentation?” — the answer is NO. It just produces less of it.

🧠 Memory Trick — The 4 Values

People → Product → Collaboration → Flexibility. In that priority order. People first, rigid plans last.


7. Key Agile Roles — Who Does What

👤

Product Owner (PO)

Owns and prioritises the product backlog. Represents customer value. Decides WHAT gets built and in which order. All changes go through PO first.

🧭

Scrum Master

Facilitates the Scrum process, removes impediments for the team, and coaches Agile practices. Sometimes called the PM or coach in Agile projects.

👥

Development Team

Self-organising, cross-functional team that does the actual work. Decides HOW to build what the PO prioritised. No hierarchy within the team.

📌 EXAM TIP — Change Requests in Agile

In Agile, when a stakeholder wants to add a new feature: → Log it in the Product Backlog → Product Owner reviews and reprioritises → Team picks it up in a future sprint. There is no CCB (Change Control Board) in Agile. CCB = Traditional only.


8. Traditional vs Agile — Side by Side

🏛️ Traditional (Predictive / Waterfall)
⚡ Agile (Scrum)
Fixed scope upfront — all requirements defined before work starts
Flexible scope — requirements evolve through sprints and feedback
Changes go through Change Control Board (CCB) with formal requests
Changes go to Product Owner → added to backlog → reprioritised
Deliver at the end — one final product handed over at project close
Deliver continuously — working product at end of every sprint
PM manages scope, schedule, cost — command and control style
Scrum Master facilitates — servant leadership, team is self-organising
Detailed upfront plan — Gantt charts, WBS, milestones
Sprint planning each cycle — backlog, sprint goals, daily standups
Low customer involvement after requirements are signed off
High customer involvement — feedback at end of every sprint
Best for: predictable, well-defined projects (construction, manufacturing)
Best for: uncertain, evolving scope (software, digital products)

9. Agile Metrics — What Gets Measured

🚀
Velocity

How many story points (units of work) the team completes in one sprint. Used to forecast future sprints.

Sprint 1 = 20 points, Sprint 2 = 24 points → Avg velocity ≈ 22 points/sprint

⏱️
Cycle Time

Time taken to complete ONE task from start to finish. Measures team efficiency at the individual task level.

Task started Monday, finished Friday → Cycle time = 4 days

📉
Burndown Chart

Shows remaining work (story points) over time across a sprint or release. Should trend downward to zero by sprint end.

If the line is above the ideal — team is behind. Below — team is ahead.

🌊
Cumulative Flow Diagram

Shows how work flows through stages (To Do → In Progress → Done) over time. Identifies bottlenecks where work piles up.

Wide “In Progress” band = bottleneck. Work is starting but not finishing.


10. Hybrid Approach — Best of Both

Definition

A Hybrid approach combines Traditional (Predictive) and Agile in the same project — using a fixed high-level structure while building features iteratively.

🏥 Real Example — Large Pharma Digital Platform

Traditional part: Overall roadmap is fixed — regulatory timeline, budget, milestone dates. These cannot change.

Agile part: Individual features (patient portal, doctor dashboard, content modules) are built in 2-week sprints with continuous feedback from medical writers and compliance teams.

👉 Hybrid works best when you have stable governance requirements (compliance, budget, deadlines) but uncertain feature details. Very common in pharma and healthcare digital projects.


11. Quick Summary — Everything at a Glance

ConceptOne-line meaningExam trigger word
Fixed PriceAgreed price — seller bears all cost overrun risk“well-defined scope” / “most risk for seller”
Time & MaterialPay per hour + materials — shared risk“hourly rate” / “unclear scope, small work”
Cost PlusReimburse all costs + fee — buyer bears most risk“research” / “uncertain scope” / “most risk for buyer”
FormingTeam meeting, polite, unclear roles — PM directs“just meeting” / “getting to know each other”
StormingConflict and disagreements — PM coaches“conflict” / “disagreements” / “tension”
NormingTeam settles, rules established — PM supports“trust building” / “roles clear”
PerformingHigh output, self-directed — PM delegates“high productivity” / “self-managing”
AdjourningProject ends, team released — PM celebrates“project closing” / “team dispersing”
Collaborate / Problem-SolveWin-win — always PMP’s best conflict answer“conflict” (almost every time)
Withdraw / AvoidIgnore conflict — always the worst option“ignore” / “walk away”
Theory XManager assumes people dislike work — micromanages“closely monitored” / “strict control”
Theory YManager trusts people are self-motivated — gives autonomy“autonomy” / “self-directed”
Hygiene FactorPrevents dissatisfaction but doesn’t motivate (salary, security)“adding salary won’t motivate” / “prevent dissatisfaction”
MotivatorDrives actual satisfaction (achievement, recognition, growth)“what actually motivates” / “recognition”
Product OwnerOwns backlog, prioritises features, represents customer“backlog” / “prioritise” / “change in Agile”
Scrum MasterFacilitates Scrum, removes impediments, coaches team“remove impediment” / “facilitate” / “coach”
VelocityStory points completed per sprint — predicts future pace“how much work per sprint”
Burndown ChartShows remaining work — should trend to zero“remaining work” / “sprint progress”
Agile change requestGoes to Product Owner → backlog → next sprint“new feature in Agile” / “mid-project request”
HybridFixed structure (Traditional) + iterative delivery (Agile)“fixed timeline but flexible features”

🎯 Practice Q&A — Test Yourself

Think of your answer first. Then click to reveal.

Q1. The project scope is highly uncertain and involves new drug research. Which contract type is most appropriate?
Answer: Cost Plus. When scope is highly uncertain and unpredictable — especially in R&D — Cost Plus is appropriate. The buyer reimburses all actual costs plus a fee. The buyer accepts the cost risk because nobody knows how expensive the work will be upfront.
Q2. Which contract type puts the most financial risk on the SELLER?
Answer: Fixed Price (FFP). The seller agrees to a set price upfront. If the work costs more than expected — the seller absorbs the loss. This motivates the seller to be efficient, but it also means the seller is taking a big risk on the estimate being accurate.
Q3. Two team members are in a heated disagreement about the technical approach. What is the BEST action for the PM?
Answer: Collaborate / Problem-Solve. Work with both parties to understand each perspective and find a solution that satisfies both. This is always PMP’s preferred answer for conflict — unless the question specifies a crisis or time-critical situation where Force/Direct may be needed.
Q4. The team is newly formed. Members are polite and getting to know each other, but roles are unclear. Which Tuckman stage is this?
Answer: Forming. The first stage — team members are meeting, being polite, and figuring out how they fit in. Roles are unclear. The PM’s job here is to Direct and Guide — provide structure and clarity until the team finds its footing.
Q5. In Agile, a stakeholder requests a new feature in the middle of a sprint. What should happen?
Answer: The request is logged in the Product Backlog. The Product Owner reviews it and decides whether to add it and where to prioritise it. The team will pick it up in a future sprint during sprint planning. Mid-sprint interruptions are not added to the current sprint without PO decision.
Q6. A manager closely monitors employees, gives strict instructions, and uses punishments for poor performance. Which motivation theory does this reflect?
Answer: Theory X (McGregor). Theory X assumes people dislike work and must be controlled, directed, and threatened with punishment to perform. Theory Y assumes the opposite — people are self-motivated and thrive with autonomy. PMP exams favour Theory Y as the better leadership approach.
Q7. According to Herzberg, will increasing salaries motivate the team to perform better?
Answer: No — salary is a Hygiene Factor. According to Herzberg, hygiene factors (salary, job security, working conditions) prevent dissatisfaction when present — but they do not create motivation. To truly motivate the team, you need Motivators: recognition, achievement, interesting work, and growth opportunities.
Q8. What is the difference between velocity and cycle time in Agile?
Velocity = how many story points the entire team completes in one sprint. Measures sprint-level throughput. Used to predict future sprint capacity.

Cycle Time = how long it takes to complete ONE task from start to finish. Measures individual task efficiency. Shorter cycle time = faster delivery of individual items.

Page 7 complete. You have now covered all major knowledge areas. Next up: Quick Revise page — all exam triggers, rapid-fire tables, and the night-before checklist in one skimmable page.

Scroll to Top