Project Management Foundations — Module
Revision Guide
1. SMART Goals
SMART goals ensure clarity and accountability. Specific: Clear and focused. Measurable: Includes
metrics. Attainable: Realistic and achievable. Relevant: Aligns with business goals. Time-bound:
Has a deadline. Example: Increase customer satisfaction score from 4.1 to 4.5 within 3 months. Tip:
If a goal lacks numbers or deadlines, it is not SMART.
2. Objectives & Key Results (OKRs)
Objective: Qualitative goal describing what you want to achieve. Key Results: Quantitative metrics
showing progress. Example: Objective: Improve customer experience. KR1: Increase satisfaction
score from 4.0 to 4.6. KR2: Reduce complaint resolution time from 24 hrs to 8 hrs. KR3: Increase
repeat customers by 15%. Best Practices: • Objectives = inspiring and directional • Key Results =
measurable and time-bound • 2–5 key results per objective
3. Project Scope
Project scope defines what is included and excluded. Includes: • Deliverables • Tasks and work
required • Deadines and constraints Out of Scope: • Items not agreed upon • Extra features without
approval Why scope matters: Prevents confusion, protects timeline and budget, ensures clarity.
4. Scope Creep
Scope creep occurs when additional work is added after project approval without proper review.
Causes: • Unclear requirements • Stakeholder requests mid-project • Lack of change control
Prevention: • Document requirements clearly • Define out-of-scope items • Establish change control
process • Communicate impacts on time & cost
5. Triple Constraint
Projects balance three constraints: Scope — what work must be done Time — schedule &
deadlines Cost — budget & resources Changing one affects others. Examples: Increase scope →
increases time & cost Reduce time → increase cost or reduce scope Reduce budget → reduce
scope or extend timeline
6. Success Criteria & Metrics
Success criteria define how project success is measured. Common metrics: • On-time delivery •
Within budget • Product quality • Customer satisfaction • User adoption • Performance metrics
Success criteria must be defined at project start.
7. Launch vs Landing a Project
Launch = delivering final output to client/users. Landing = measuring impact and ensuring
outcomes were achieved. Launch example: Website goes live. Landing example: Traffic increases
by 25% within 3 months. Projects are successful only when they LAND, not just launch.
8. Tracking & Communicating Success
Track performance using metrics and dashboards. Methods: • Surveys & feedback • Usage data &
adoption rates • Performance indicators • Stakeholder reviews Communicate results through: •
Reports • Presentations • Dashboards • Review meetings
9. Stakeholders & Customer Focus
Stakeholders include anyone impacted by the project. Key actions: • Understand expectations •
Maintain communication • Align goals with stakeholder needs • Manage feedback & approvals
10. Change Control Process
Steps to manage changes: 1. Submit change request 2. Assess impact (scope, cost, time) 3.
Approve or reject 4. Update project plan 5. Communicate changes This prevents uncontrolled
scope creep.
11. Common Exam Traps & Clarifications
• Scope change = adding new deliverables. • Delay ≠ scope creep (it is schedule risk). • Cost
increase ≠ scope creep (budget issue). • Success criteria ≠ tasks completed. • Objectives =
direction; Key Results = numbers. • Attainable means realistic, not easy.
12. Real-World Retail Examples
SMART Goal: Reduce billing wait time from 20 minutes to 10 minutes within 2 months. OKR
Example: Objective: Improve in-store customer experience. KR1: Increase conversion rate by 10%.
KR2: Increase customer rating from 4.1 to 4.5. KR3: Reduce customer complaints by 30%. Scope
Example: Included: Billing counter redesign. Out of scope: Store layout redesign.
13. Quick Memory Framework
SMART → Clear goals OKR → Direction + measurement Scope → Boundaries Scope Creep →
Uncontrolled expansion Triple Constraint → Balance Launch → Deliver Land → Achieve results
Success Criteria → How success is measured