PMBOK® 8 – The Big Picture: From Confusion to Clarity

After completing this lecture, students will be able to:

• Understand why PMBOK® 8 moved away from being process-heavy and rule-driven

• Explain PMBOK® 8 as a decision-making and value-focused mindset, not a checklist

• Identify the three major changes introduced in PMBOK® 8:

  • Simplified, decision-oriented principles

  • Reframed focus areas instead of rigid phases

  • Processes as flexible guidance rather than mandatory steps

• Recognize how PMBOK® 8 reflects real-world project behavior, where adaptability matters more than fixed structures

• See PMBOK® 8 as a connected system, not disconnected sections

After completing this lecture, students will be able to:

• Understand the two-part structure of PMBOK® 8 and why it is designed this way

• Clearly differentiate between:

  • Part 1: Mindset and thinking (value, behavior of projects, decision-making)

  • Part 2: Application and execution (domains, processes, tools, and artifacts)

• Recognize the risk of using tools without understanding context or intent

• Apply PMBOK® 8 in the correct sequence: think first, then act

• Read and interpret PMBOK® 8 in the way PMI intended, not as a disconnected reference book

After completing this lecture, students will be able to:

• Explain why PMBOK® 8 defines project success in terms of value, not task completion

• Understand how value is created and realized as a system, not through isolated activities

• Describe the strategy-to-execution flow:

  • Strategy flowing downward from organization to project

  • Value flowing upward from project outcomes to organizational benefits

• Distinguish between delivery completion and value realization

• Recognize the project manager’s role in protecting and enabling value throughout the project lifecycle, not just delivering outputs

After completing this lecture, students will be able to:

• Understand why projects exist as responses to product or service evolution, not as isolated activities

• Explain the relationship between product life cycle stages and project initiation

• Identify how different product stages require different project approaches:

  • Early-stage products → flexibility, experimentation, and fast feedback

  • Mature products → stability, control, and optimization

• Recognize why applying the same project strategy to all situations leads to planning failures

• Understand how portfolios, programs, and projects collectively support product value

• Clarify the role of Product Owners and Business Analysts in maintaining alignment between delivery and real needs

• Interpret project success as moving product value in the right direction, not just completing deliverables

After completing this lecture, students will be able to:

• Understand why projects fail due to missing or weak functions, not because of missing tools or methodologies

• Explain the concept of the 7 Core Functions behind every project as defined in PMBOK® 8

• Clearly differentiate between functions (responsibilities) and job titles

• Identify and explain each of the seven essential project functions:

  • Oversight and coordination

  • Feedback management

  • Facilitation and support

  • Execution of work

  • Applied expertise

  • Direction and insight

  • Adequate resources

• Recognize how these functions apply across all project types, regardless of size, industry, or delivery approach

• Assess whether all seven functions are adequately covered in a project, even when roles are combined or distributed

• Shift focus from asking “Who has which title?” to asking “Are all critical functions being performed at the right time?”

After completing this lecture, students will be able to:

• Understand why PMBOK® 8 places people at the center of project movement and success

• Identify the shift from titles, hierarchy, and control to responsibilities, competencies, and collaboration

• Explain how project success is driven by capability and interaction, not by position or authority

• Recognize the key capability areas that effective teams combine, including:

  • Power skills such as communication and emotional intelligence

  • Business acumen to understand purpose and value

  • Appropriate delivery approaches (predictive, agile, hybrid)

  • Results orientation and responsible use of technology

• Understand technology’s role as an enabler of people, not a replacement

• Explain how sponsors, customers, product owners, teams, and users connect strategy, execution, and value realization

• Identify how breaks in collaboration or feedback loops lead to value leakage in projects

After completing this lecture, students will be able to:

• Understand why PMBOK® 8 is principle-based, emphasizing mindset over checklists or rigid tools

• Explain how principles guide decision-making in complex and uncertain project environments

• Apply holistic thinking to evaluate how decisions impact scope, cost, risk, stakeholders, and long-term outcomes

• Distinguish between delivering outputs and realizing value, using the Focus on Value principle

• Interpret built-in quality as a mindset embedded in work design, not a final inspection step

• Understand accountable leadership as responsibility and clarity, not authority or control

• Recognize the importance of sustainability and long-term impact in project decisions

• Explain how an empowered culture improves speed, decision quality, and early risk identification

• Use principles as directional guidance, supporting judgment and context-driven choices before selecting tools or processes

After completing this lecture, students will be able to:

• Understand what PMBOK® 8 means by adopting a holistic view of projects

• Explain the concept of a project as a system, where elements interact rather than operate in isolation

• Identify interdependencies across scope, schedule, cost, risk, and stakeholders, and understand their impact on decision-making

• Recognize the importance of continuous alignment with organizational strategy

• Apply system-wide risk thinking, identifying how risks move across different project areas

• Evaluate project decisions based on their long-term and sustainable impact, not just short-term fixes

• Use holistic thinking to anticipate ripple effects and make better decisions in complex project environments

After completing this lecture, students will be able to:

• Clearly distinguish between outputs (what is delivered) and outcomes (the real-world impact created)

• Understand why delivery success does not automatically mean value realization

• Recognize the critical role of adoption and usage in determining project value

• Apply the mindset of continuously asking: “Are we still creating the impact we promised?”

• Understand why value evaluation is a recurring decision point, not a one-time checkpoint

• Identify appropriate responses when value becomes unclear, including adapting, simplifying, or stopping a project

• Interpret professional judgment as choosing impact over activity and value over effort