Chapter 1 – Introduction to Project Management
Definition of a Project:
- A temporary endeavor undertaken to create a unique product, service, or result (PMBOK Guide).
- Requires organized work efforts, a defined beginning and end, unique stakeholders, and is subject to time
and resource limitations.
Definition of Project Management (PM):
- Application of knowledge, skills, tools, and techniques to project activities to meet project requirements.
- Processes: Initiating, Planning, Executing, Monitoring/Controlling, Closing.
- Trade-offs among: Scope, Quality, Cost, Schedule, Resources, Risks.
History of Project Management:
- Emerged formally in the 1950s in aerospace and construction.
- Agile introduced in 2001 for adaptive planning.
- Recent focus on communication, leadership, and teamwork.
Projects vs. Operations:
- Projects: Temporary, unique outcomes.
- Operations: Ongoing, repetitive activities.
Skills Needed:
- Soft Skills: Communication, Leadership, Conflict resolution.
- Hard Skills: Risk analysis, Quality control, Scheduling, Budgeting.
Project Life Cycle:
1. Selecting and Initiating
2. Planning
3. Executing (includes monitoring/controlling)
4. Closing and Realizing
PMBOK® 5 Process Groups:
- Initiating, Planning, Executing, Monitoring & Controlling, Closing.
PMBOK® 10 Knowledge Areas:
- Integration, Scope, Schedule, Cost, Quality, Resource, Communications, Risk, Procurement, Stakeholder.
PMI Talent Triangle:
- Technical PM + Leadership + Strategic & Business Management + Digital Skills.
Project Goals & Constraints:
- Performance goals: Scope, Quality.
- Constraints: Time, Cost, Resources, Risk.
1
Project Success Factors:
- Clear requirements, User involvement, Adequate resources, Executive support, Realistic schedules, Good
planning.
Agile Principles & Values:
- 12 Principles and 4 Values (Individuals over processes, Customer collaboration over contracts, Responding
to change over following a plan, Working product over documentation).
Diagram/Table Example: - Exhibit 1.3: Project Customer Trade-Off Matrix – Shows balance between cost,
schedule, and specifications versus customer, organization, and team success.
Chapter 3 – Chartering Projects
Definition:
- A Project Charter is an informal contract between sponsor and team.
- Authorizes the project, defines boundaries, clarifies purpose.
Purposes of a Charter:
1. Authorize the project manager.
2. Create common understanding.
3. Commit team and sponsor to project spirit.
4. Screen out poor projects early.
Typical Charter Elements:
- Title
- Scope Overview (boundaries, product scope, avoid scope creep)
- Business Case (why project is needed, alignment with strategy)
- Background (context, optional)
- Milestone Schedule & Acceptance Criteria
- Risks, Assumptions, Constraints
- Resource Estimates (budget, authority)
- Stakeholder List
- Team Operating Principles (meetings, respect, decision-making)
- Lessons Learned
- Signatures and Commitment
Constructing a Charter:
- Sponsor drafts Scope & Business Case.
- Leadership/team adds details.
- Ratification involves signatures of sponsor, PM, and core team.
Agile vs. Predictive Charter:
- Agile: Informal, evolving roadmap, approved by product owner, decisions delayed until latest responsible
moment.
- Predictive: Formal, milestone-driven, detailed upfront.
2
Diagram/Table Example: - Exhibit 3.3: Charter Elements and Questions Answered – Summarizes
purpose of each element.
- Exhibit 3.5: Milestone Schedule Template – Outlines milestones, acceptance criteria, responsible
stakeholders, and due dates.
MS Project Applications:
- Initialize project, set start date, create summary tasks, define milestones, and visualize schedules via Gantt
charts.
Chapter 6 – Stakeholder Analysis and Communication Planning
Stakeholders:
- People, groups, or organizations impacted by project work or outcomes.
- Examples: Project team, resource providers, regulators, users, community.
Stakeholder Analysis:
- Process of gathering & evaluating stakeholder information to prioritize interests.
- Prioritization based on: Power, Legitimacy, Urgency.
Stakeholder Register:
- Repository of all stakeholder information (roles, interests, influence).
- Helps capitalize on support & mitigate resistance.
Engagement Assessment Matrix:
- Tool to define engagement levels (e.g., unaware, resistant, neutral, supportive, leading).
- Becomes part of the stakeholder management plan.
Building Relationships:
- Open communication, shared learning, joint agenda setting, celebrating successes.
- Values: Early involvement, Responsiveness, Transparency, Reliability.
Stakeholder Engagement Management:
- Share documents, clarify assumptions, document deliverables, follow change control.
- Monitor satisfaction regularly.
Communication Plan:
- Living document, part of PM plan.
- Purposes: Manage expectations, ensure work quality, knowledge management.
- Includes: Communication matrix, methods, frequency, responsibility.
Communication Matrix Questions:
- Who needs information? What information? When? How? Who delivers it?
3
Meeting Management:
- Types: Planning, Decision-making, Progress verification, Issue resolution, Closure.
- Improvement via PDCA cycle.
Issues Log:
- Living document capturing unresolved issues, decisions, and action items.
Agile Communication Methods:
- Emphasis on transparency, adaptability, and short cycles.
- Meetings include: Product backlog refinement, Sprint planning, Daily stand-ups, Demonstrations,
Retrospectives.
- Use of information radiators (visible progress charts).
Diagram/Table Examples:
- Exhibit 6.2: Stakeholder Identification & Prioritization Matrix – Plots stakeholders based on power,
legitimacy, urgency.
- Exhibit 6.11: Project Communications Matrix – Outlines who needs what info, when, and how.
- Exhibit 6.16: Issues Log Template – Tracks open and closed issues with actions.
✅ These notes include key definitions, lists, and diagrams/tables mentioned in the slides. They are
structured chapter-wise for clarity and detailed study.