Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Hybrid Project Management: PMBOK 7, Process and Change [EN]
Rating: 5.0 out of 5(5 ratings)
2,804 students

Hybrid Project Management: PMBOK 7, Process and Change [EN]

hybrid project management | PMBOK 7 | project management | agile | waterfall | BPMN | change management | influence
Last updated 8/2026
English
English [Auto],

What you'll learn

  • Run a project through the full PMBOK 7 cycle: charter, scope, work breakdown, network diagram, Gantt, three-stage budget, control and closure
  • Choose the delivery approach per project rather than applying the same one everywhere, using the life cycle domain
  • Describe a process in BPMN so that someone else can run it without asking you questions
  • Deliver a change through Kotter's eight steps and handle the resistance that shows up around step four
  • Run an organisational intervention end to end and calculate its ROI with Kirkpatrick and a balanced scorecard
  • Get executive buy-in with no formal authority over anyone involved
  • Write a brief that produces a decision instead of a request for more information
  • Keep a project alive through a crisis using decision protocols rather than improvisation
  • Learn alongside Mike's 1.6 million students from 185 countries
  • Get the author's experience from Preply, Wargaming, iDeals and Alfa-Bank

Course content

5 sections12 lectures5h 17m total length
  • What Project Management Is: PMBOK 7 Principles and Domains36:56
    • What a project is, and the four stages every one goes through

    • Project management as a way of delivering a result

    • The role of the project manager and the main difficulties of the job

    • The PMBOK 7 principles and performance domains in practice

  • Creating a Project: Business Case, Charter and Cost-Benefit Analysis27:00
    • Collecting the ideas and turning one into a business case

    • Developing the charter

    • Cost-benefit analysis and the documentation

    • Choosing which project actually gets done

  • Stakeholders: Listing Them, Ranking Them and Planning Engagement23:50
    • Who your stakeholders are, including the ones nobody listed

    • Compiling and prioritising the list

    • Ways of engaging them

    • Assessing influence and interest, and planning the engagement

Requirements

  • A project, or a serious intention to run one. Every section produces a document
  • No certification needed. PMBOK 7, BPMN and Kotter are all introduced from the beginning
  • Comfort with the idea that you will be responsible for people who do not report to you
  • English at intermediate level or above, since all lessons are in English
  • A spreadsheet for the schedule, budget and evaluation exercises

Description

This course contains the use of artificial intelligence.

A project can finish on time, on budget and to specification, and change nothing about how the organisation works.

Six months later people are doing what they did before, with the new system open in a tab nobody clicks.

Why delivery is not the same as change

The methodology argument gets most of the attention — predictive against adaptive, Gantt against sprint — and it is the least interesting part of the problem. A plan can be correct and still fail, because the process underneath was never described, so the new way has nothing to replace. Or because the people affected were informed rather than involved, and informed people comply until you stop watching. Or because you had responsibility for the outcome and authority over nobody, and nobody told you that is the normal condition of the job.

How the course is built

Thirty-six lessons in four parts. Delivery first, ten lessons on PMBOK 7 — which is deliberately methodology-agnostic, so the choice between predictive, adaptive and hybrid becomes a decision you make per project rather than a religion you belong to. Business case, charter, stakeholder analysis, scope, work breakdown, network diagram, Gantt, the three stages of a budget, uncertainty, the matrix environment, control and a real closure.

Then the process layer. Six lessons on describing how work actually happens: methodology, flowcharts, BPMN, tools, and running a description project from concept through defending it to management and closing it. This is the part that decides whether your change has anything to attach to.

Change, intervention and getting agreement

Then six lessons on change itself: the eight mistakes, Kotter's model, generating urgency that is not manufactured, the rider-and-elephant model for the emotional half, quick wins, and fixing a change into the culture so it survives your departure.

Then eight lessons on organisational development, which is change management with a full method underneath it — entry, diagnosis, intervention at four levels, and evaluation including ROI, Kirkpatrick and a balanced scorecard.

And finally six lessons on the thing nobody teaches project managers: operating with responsibility and no authority. Managing a senior person's attention, writing a brief that ends in a decision rather than a request for more analysis, working the informal power structure, and holding things together in a crisis.

Who is teaching this

Mike, the number one HR instructor on Udemy. More than 1.6 million course enrolments, over 150,000 professionals trained, PHRi and SHRM-CP certified, HRCI representative in more than 10 countries. I built the people function of the unicorn Preply and worked at Wargaming, Alfa-Bank and iDeals. Most of what I know about the authority problem I learned delivering projects across functions that had no obligation to cooperate with me.

What is included

  • Lifetime access to all course materials

  • Active instructor support in the Q&A section

  • Udemy Certificate of Completion

  • Practical assignments and real business cases

  • A section with additional courses, tools and resources

Before lesson one

Think of a project that was delivered and then quietly undone. Write one sentence on why. Whatever you wrote, this course will probably give you a second reason you did not consider, and the second one is usually the real one. Enrol now and start the first lesson today.

Who this course is for:

  • Project managers who learned one methodology and keep meeting projects it does not fit
  • Specialists running their first real project, with a plan and no framework underneath it
  • Operations, HR and finance leads delivering change alongside their day job
  • Business analysts and process owners who describe how work should happen and watch it not happen
  • Transformation and PMO people whose projects finish on time and change nothing
  • Consultants delivering into organisations where they have no authority at all
  • Anyone whose projects are technically successful and quietly abandoned afterwards