シャドーイング練習: Inside PMBOK Guide 8: What Project Managers Must Know | Episode 542 - 動画で英語スピーキングを学ぶ
練習モードを選ぶ
各モードは全画面の練習ルームで開きます。
677 文
文が短すぎたり長すぎる場合は、Editをタップして調整してください。
1
So you think you know what a project is?
2
Well, think again.
3
Hello and welcome back to the Project Management Podcast at pm-podcast.com.
4
This is episode 542 and I am a very excited Cornelius Fichtner here on the podcast.
5
Thank you so much for joining us here today.
6
I am very excited because, well, the PMBOK Guide 8 edition has dropped.
7
It is built from tens of thousands of data points collected from real practitioners.
8
And it shows the structure is cleaner.
9
The guidance is really more practical.
10
And the entire document reflects how projects actually unfold rather than
11
how we would sometimes like to imagine they should unfold on paper and our schedules and you know how it goes.
12
It is a deliberate move towards clarity,
13
usability and the relevance for the work that we project managers do every single day.
14
The eighth edition also updated the definitions for several foundational concepts that many of us assumed were set in stone.
15
And that includes the definition of both project and project management, which is why I started today's episode with,
16
so you think you know what a project is?
17
We'll see those new definitions later on.
18
Guiding us through the thinking behind these changes is Jesse Fuel.
19
Jesse has coached leaders on five continents, shaped multiple certifications and standards,
20
and served as the chair of the PMBOK 8 development effort.
21
He brings a front row view of what the global community asked for and how those insights shaped this new edition.
22
And here he is.
23
Welcome, Jesse Field.
24
Thank you for joining us today.
25
It is an absolute treat, Cornelius.
26
I'm excited to be back on the podcast and to talk about this new exploration,
27
definition, formalization of what it means to do project management.
28
Wonderful.
29
Thank you so much.
30
And as the chair of PIMBOK 8, Wayne's World, we are not worthy.
31
We are not worthy.
32
Thank you so much for having you here.
33
All right.
34
We already got the first comment here coming in.
35
Greetings from Azerbaijan.
36
We have a worldwide audience with us.
37
Welcome to you, Cameron.
38
Yeah.
39
As always, this is a video episode.
40
If you're only getting the audio, please stop by at pm-podcast.com slash 542 slash YouTube or slash Spotify.
41
I before we start this interview, there is one thing that I need to get off my chest.
42
That's this here.
43
The PMP exam is not a test of the PMBOK guide.
44
Repeat, not a test of the PMBOK guide.
45
Reading the PMBOK guide will help, yeah, sure.
46
But it's only one of many resources that you need to use as you are preparing for your PMP exam.
47
With that out of the way, let us begin.
48
Jesse, how was the 8th edition developed and what problems or gaps is it really designed to solve for today's project managers?
49
Well, Cornelius, there's really two key themes.
50
The first one is that there is a regular renewal cycle that is required by ANSI,
51
which is the standards body that accredits the PMBOK Guide as the global standard for project management.
52
And their requirement is
53
that the document is updated on a regular cadence every few years in order to reflect any evolutions
54
and variations and changes in the industry in the global marketplace.
55
So there will be a ninth edition.
56
It's coming in a few years, the same way that this has been on a regular recurring cycle.
57
So that's point number one.
58
There's been a lot of practitioners who complain, why do they keep changing things?
59
And it's because the world keeps changing.
60
And it's the accrediting body's position that the standard of practice should reflect evolution
61
and nuances and ebbs and flows in the industry
62
so that's point number one um which is that uh it changes the order of life
63
um but the deeper question i think you're asking is why were specific changes made it um 48th edition is that is
64
that a fair fair yes yes yeah okay the the the the seventh edition was intentionally disrupted the seventh edition
65
which was released in 2021 reformatted what was traditionally understood to be knowledge areas process groups inputs tools techniques and outputs
66
and just blew it up completely in order to shake up the community shake up the profession to wake up
67
that things are changing in the world
68
and at the same time move to a principle-based standard of
69
project management as opposed to a process-based standard of project management as you can imagine there was mixed response to
70
that and so the eighth edition was launched with the conviction
71
that this will be not about opinions not about disruption it will be the most data-driven project management standard in history.
72
And it is, as I think you've alluded to a little bit already.
73
Yeah, you had like what, like 15,000 comments from people that you had to go.
74
Did you read each one of them?
75
Not you personally, right?
76
You had as the chair, you're at the top, you have two dozen.
77
Yeah, there were two dozen volunteers involved.
78
There was It was a double-blind process of 12 development team volunteers and then 12 review team volunteers.
79
None of them knew who the other was, and I was the chair kind of as the anonymous bridge between them.
80
And yes, we looked at every single comment.
81
And the review team had their own comments before the 15,000,
82
such that by the time the 1,500 contributors saw the draft, it had already been vetted a little bit.
83
And that's even after the market research went into understanding what the community wanted in the eighth edition.
84
All right.
85
So much for the story behind the PMBOK Guide.
86
Now, let us open it up.
87
Our plan is to take the PMBOK Guide eighth edition table of contents and discuss some handpicked topics.
88
It's quite thick.
89
Let's see.
90
I have it right here.
91
294 pages.
92
We can't look at everything.
93
And what we see here is a simplified version of the table of contents.
94
Generally speaking, it consists of three segments.
95
The standard for project management is first.
96
Then the actual PMBOK guide is second.
97
And then we have sort of the back matter, the extras and all of that.
98
And Jesse, for those who don't know, what is the difference between the standard and the PMBOK guide?
99
This is the third edition in a row that has differentiated between those two different parts of the document.
100
The document, the first half of the document is what is accredited by ANSI as a standard for project management.
101
It goes through additional extra validation and governance to make sure
102
that there are opportunities for community comment and that there is a consensus vote from a committee and all of those things.
103
And that's where the most, what we believe to be the most important fundamental elements of project management are located.
104
The second part, which is sometimes called the guide or sometimes called the body of knowledge, is more about the how.
105
It's more about some of the tools that we like to use in project management,
106
which are very contextual, very nuanced, and can be tailored in or tailored out.
107
the standard includes the things that are universal.
108
The guide or the body of knowledge includes things that are a little bit more contextual and case by case.
109
Okay.
110
Thank you very much.
111
And from my perspective, as a practitioner, you need to read both, right?
112
You can't just say, oh, I'm just following the standard, or I'm just going to read the PMBOK guide, or I'm just going to read the appendices.
113
Yeah, not going to help you much there, but you You need to understand the content of the law
114
in order to really know how to manage a project in its entirety.
115
And some people will find that the content in the body of knowledge,
116
that second part, it's kind of the more interesting stuff.
117
It's where the rubber meets the road.
118
It's kind of where we get nerdy and technical.
119
And yet we also want to make sure that people don't skip over that standard part.
120
So it used to be second.
121
I remember in previous editions it was in the back.
122
It was kind of hidden and nobody knew about it.
123
And now it's first.
124
So yeah, emphasis is right there.
125
All right.
126
Let us now head over.
127
So for the rest of the conversation, this is the actual table of contents here.
128
And let us begin with the system for value delivery,
129
which is the second item there in the standard.
130
Would it be correct to say,
131
Jesse, value and the system that describes it is really at the core of what a project is supposed to do?
132
Deliver value?
133
A hundred percent.
134
This has been a conversation that's been evolving and intensifying, I would say, over the last 10 to 15 years
135
which is that the project management of the 20th century was get it done.
136
Project management of the 21st century is, was it worth it?
137
And just because it's done doesn't mean it was worth it.
138
And so we're being challenged more and more in every sector, in every country, in every industry.
139
Do you even know why we're doing this?
140
And can you make the case that we should keep going? and
141
and usually uh project managers are historically project managers have said
142
that's above my pay grade it's not my job to be
143
able to articulate whether what i'm doing is even worth doing
144
and that's more of a portfolio discussion or a sponsor discussion
145
and what we're finding in the marketplace is change is happening
146
so fast that our sponsors can't even articulate the value proposition of their projects.
147
They need help from you, project manager, to ask tough questions.
148
Why are we doing this?
149
Who are the stakeholders who benefit?
150
Who are the stakeholders who would not benefit?
151
What's kind of an impact?
152
How would you measure that impact?
153
These are the kinds of questions that we're being expected to bring to bear
154
and articulate the value of a project within an organization or even within an ecosystem of vendors and suppliers.
155
It's more than just get it done.
156
Excellent.
157
And people do agree.
158
We have LinkedIn user saying that is the truth.
159
Next, let us zoom in here because you gave us a good segue.
160
Was it worth it?
161
Let us zoom in here on 2.1.2, assessing project success.
162
I have the definition of project success over here.
163
Let me read this for everybody.
164
Project success is defined as the consensus view across intended beneficiaries,
165
other stakeholders, and project participants,
166
that a project was perceived to have delivered value that was worth the effort and expense.
167
And now let me highlight two words in this definition,
168
consensus and perceived, because this definition clearly says that a consensus of how the participants perceive a project is what counts.
169
So even if the project is behind schedule, over budget, and all of that,
170
if the consensus of your stakeholder says, No, you know what?
171
Yeah, yeah, yeah.
172
These are all issues, but we solved them.
173
In the end, this project was still worth it.
174
That is an important thing to realize.
175
Jesse, would you highlight different words here?
176
Is there anything else that you might want to highlight?
177
Oh, my goodness.
178
I like the way that you highlighted this um there's a couple of reasons
179
and um then there's a concrete example
180
so first consensus does not mean unanimous nor does it mean
181
strictly from the highest uh the hippo the highest paid person's
182
opinion the consensus really is a like on the whole maybe it's a majority maybe it's a plurality
183
and uh and so so that's the key number point
184
and the other one is that value perceived is value achieved
185
that um because value is hard to measure this is one thing
186
that the agilists have have I think not been able to
187
articulate well the agilists have been promoting deliver value focus on value how do I measure
188
that we don't know okay so then value is in the eye of the beholder we have net motor score,
189
we've got customer satisfaction, we've got ROI.
190
So depending on your context, your metric might be different.
191
So then the value is really going to end up being contextual and perception-based.
192
Just think, here's the example, about the Sydney Opera House.
193
The Sydney Opera House is mentioned in the guide as the classic example of 10x over budget,
194
5x over schedule um the the uh pm of australia lost their job
195
because the project was being was was undergoing
196
so much just upheaval there was a riot on the construction site of the sydney opera house
197
and it's a it's a un it's a unesco heritage site
198
it's considered it's a success world it is heralded as you know like one of the greatest architectural achievements of mankind
199
It is the symbol of the Sydney skyline.
200
So was it worth it?
201
Yeah.
202
It's considered to be one of those failed projects that was totally worth it.
203
Yeah.
204
Let me ask you this.
205
does this new definition, this updated, this modernized definition of project success mean
206
that project managers should also change the way that they measure and evaluate success on their projects?
207
Absolutely.
208
We'll talk about it in a moment.
209
But in the guide, there's an entire domain,
210
an entire discipline around executing on a project in a way that measures project performance.
211
So one of the new processes that's introduced is to measure project performance, which is two sides.
212
There's delivery performance, schedule, risk, compliance, budget, but then there's value performance,
213
net promoter score, customer satisfaction, stakeholder satisfaction, ROI, revenue.
214
Project performance now includes both conventional, historical, traditional delivery excellence, but also on the value side.
215
Okay, wonderful.
216
Thank you very much.
217
Before we move on, let me remind everybody, we are live on Facebook, X, LinkedIn, YouTube.
218
If you have a question, please feel free to type it into the chat And we'll see if we can squeeze this in for everybody.
219
Okay, let us move on here.
220
Where are we?
221
Let's see.
222
For some reason, is my computer.
223
There we go.
224
Ah, okay.
225
It didn't want to do what I was wanting it to do.
226
We are moving on here to this, where we see the six project management principles.
227
They, let me go through them.
228
They start on the left there at 3.3 with adopt a holistic view.
229
Below 3.4, focus on value.
230
3.5, embed quality into processes and deliverables.
231
At the bottom left, 3.6, be an accountable leader.
232
Top right, 3.7, integrate sustainability within all project areas.
233
And below that, 3.8, build an empowered culture.
234
Many principles.
235
Go ahead.
236
You wanted to say something, Jesse.
237
No, I'm just like, yeah.
238
Yeah, those are the six principles of project management.
239
Right.
240
So many could have made it into this particular list.
241
What was the reasoning behind choosing these six as the universal foundation?
242
Well, it was in response to some of the practitioner feedback around the seventh edition, which actually introduced 12.
243
12, yeah.
244
And generally speaking, where the practitioners were coming back, three out of four project managers said,
245
we agree that principles matter more than processes.
246
They're both important, but at the end of the day, what makes for a successful leader are your guidelines,
247
your guiding ways of managing and leading, how you approach the like, focusing on an empowered culture,
248
so that way you can delegate effectively instead of being the center of gravity all the time.
249
That's an example of what makes for a successful project.
250
So the seventh edition was reflecting what was a community conviction
251
that their effective management and leadership is not about following a process.
252
It's about leading.
253
However, it was a little bit overwhelming, 12 of them.
254
There was some duplication, not just within the principles.
255
There were two different principles around leadership that,
256
so around accountability and leadership were two different principles here they've been merged into one
257
that seems to be a little bit more focused also the
258
uh there were some confusion about well we have a quality principle but we also have quality uh processes
259
what's the difference between a process versus a domain versus a section
260
and so we intended to remove as much duplication
261
and repetition as possible with the eighth edition
262
and just make everything simpler thank you very much um let's
263
see before we move on to the next few questions let me bring up uh these here
264
because we have a few comments
265
and questions uh can we claim pdus for this session yes i'll mention this at the end next
266
when will pinbox ip included in the pmp eco that's what
267
i mentioned at the beginning the pmp exam is not a
268
test of the pmboc guide however the new exam content outline
269
has already been published things are in alignment with the pmboc guide like the new definitions
270
and all of that
271
but it is not a test of the pmboc guide some
272
of you may have noticed me looking at the pmboc guide
273
here it is i have a copy i bought it at the global summit
274
and because of this question here does value engineering play any specific role in assessing and terminating the value.
275
I looked in the index value engineering does not seem to be mentioned in here.
276
So Jesse, and in my opinion, this matches exactly the next question as well.
277
I think product success, social benefits and major environmental impact should be added in definition.
278
To me, both these questions go a little too deep because remember,
279
it's the consensus whether I feel that it was worth it, whether the value has been achieved.
280
So if you're in your opinion, value engineering is part of it and you think,
281
no, based on value engineering, it was not achieved.
282
Well, there you go.
283
If in this opinion here, you feel that social benefit was achieved, major environmental impact, we didn't have any.
284
That is your understanding of what it means to be successful.
285
So you put these thoughts into the definition.
286
The definition is fine, I think.
287
You are trying to put more into it, which is what you need to do when you yourself are asked, was it worth it?
288
Jesse, is my interpretation here right?
289
I think you're on to something there, Cornelius.
290
at actor shayit 619 is making the point about value engineering i think
291
that would be an effective technique to make the case
292
that the project is either over performing or underperforming
293
when you're doing an executive briefing or a stakeholder presentation and so value engineering could be a way to capture,
294
identify, communicate the value that a project is delivering.
295
At Vatsal Ramesh, the project success definition is intended to be inclusive,
296
such that the context determines the societal benefit and the environmental impact or the sustainability impact.
297
Remember, sustainability is one of the core principles, and so it will go into the perception of value around a project.
298
But the definition stops short of committing the perception to just those dimensions.
299
All right.
300
We are about halfway through our conversation here today, so let us continue.
301
And from here, we are moving on to the project life cycle right here.
302
And we are going to be taking a look at two areas in the project lifecycle.
303
First of all, we have 4.2 there, the development approaches, predictive, adaptive, and hybrid.
304
And then second, we want to look at What we know as the, or what we knew as the process groups,
305
they are now under the heading of focus areas.
306
So Jesse, when we look at predictive, adaptive, and hybrid in PMBOK 8, so we're talking about the top portion here,
307
are these simply approaches that we already know, you know, agile is agile,
308
or did the team redefine them in a way that would surprise us practitioners?
309
I think it's fair to say that the predictive, adaptive, and hybrid are essentially going to be very familiar to those
310
of us who have already been working in either agile ways of working
311
or so-called waterfall approaches with more formal serial plan-driven approaches versus highly adaptive and iterative.
312
I think it's going to be mostly familiar.
313
It continues the community's usage of the term predictive versus adaptive, which was introduced back in,
314
I believe, 2013 with the fifth edition, is a way to be more inclusive.
315
The agile waterfall debate can be a little bit divisive.
316
And so for the last 12, 15 years, PMI has been intentionally using
317
that language as a way to describe a spectrum because no project is fully plan driven and predictive with zero change.
318
And no project is all adaptive, 100 percent exploratory with no concept of where we're going.
319
there's always some place where you live on that spectrum
320
and a hybrid approach tends to be a blending of different places on that spectrum at the same time.
321
Okay.
322
So it's very familiar to, it should be familiar to most people.
323
Yeah.
324
Thank you very much because this also answers this question here from Abidaz one.
325
What are the new development approaches and life cycles being emphasized
326
and how do they integrate with the principles
327
and i think nothing new i mean you did not come
328
up with a new development approach you did not come up with a new life cycle
329
but let's focus on the last one here how do they
330
integrate with the principles is there some sort of a mapping
331
table is there some sort of a combo how does this work the the what's important about the principles is
332
that they are universal foundational to every project regardless of
333
which approach you take so when we talk about embedding quality into everything we do
334
this is not simply about following quality management processes about having
335
a quality mindset in a predictive environment where maybe we have a lot of quality control and quality engineering,
336
or maybe also in an adaptive environment where there's a deep
337
lean thinking ethos where we're going to shift left on a lot of quality practices to make sure
338
that we're iterating internally to verify the work before we validate it with stakeholders.
339
In either approach, the principles like having embedding quality into everything that we do are universal regardless of approach.
340
So that's the intention there with the standard is that it's applicable to every project regardless of which approach the project takes.
341
Wonderful, thank you very much.
342
And let's not forget when you look at the development approaches here, predictive, adaptive and hybrid, and when we go back to the principles,
343
you know, focus on value.
344
Doesn't matter whether this is adaptive or hybrid.
345
Be an accountable leader.
346
Build an empowered culture, right?
347
That there is no real reason why you can't do that in one of these development approaches there.
348
Let us move down 4.5.
349
I said we'd be looking at that.
350
What prompted the development team to bring back the essence of process groups under the name focus areas?
351
Demand.
352
You heard our voices.
353
Okay, clearly.
354
Absolutely.
355
80% of all project managers in the world came back and said, hey, where did the process groups go?
356
80% of project managers saying, isn't it true that every project has some form of initiating, launching?
357
Isn't it true that every project has some element of planning and executing and that there's some level of monitor and control?
358
And eventually projects are closed out to some degree.
359
even if they're a multi-year project.
360
And so the community came back to the standards team with this demand,
361
overwhelming universal agreement that these five things are foundational to every project everywhere,
362
whether it's agile or predictive or hybrid,
363
that these five things are important they were no longer going to be tied to processes.
364
Planning happens regardless of what processes you use.
365
Execution happens regardless of which processes you use.
366
How you do your execution, your monitoring, controlling, and your planning is really up to the project-specific context.
367
So you can use processes, and we make the point of highlighting this.
368
You can use the processes, maybe use the 40 processes that we offered, or you can use informal practice instead.
369
How you go about those five focus areas is independent of the processes
370
or practices or policies or traditions or habits that you're using as long as you focus on them being done well.
371
I like the comment we got here from Dottie 102 to, it is a testament to how ingrained the focus areas are in our craft.
372
They are in our blood.
373
Yes, it is true.
374
It is true, especially if you have started like I think I started with Pimbok version two originally.
375
That was the first one that I read.
376
Oh, my goodness.
377
Yeah, it's been quite, quite a long time there.
378
And from here, we want to move on.
379
We're leaving the standard behind us.
380
We're moving to the second section of the document here, which is the PMBOK guide.
381
Here is what PMI says, what we can expect.
382
From the PMBOK guide, we can benefit from an evolved structure that connects principles, domains, and focus areas in a clear, actionable way.
383
You have already spoken towards this.
384
Where would you say that we as practitioners will feel the biggest aha moment,
385
so to say, as we navigate the new structure and review the new document?
386
I would say that for more experienced and tenured members of our community,
387
they're going to have an aha where they start seeing
388
that the processes have different names than they've been familiar with in the sixth edition or before.
389
And that the categories in which you find the processes, they're no longer knowledge areas.
390
They're performance domains.
391
and they themselves have different names for example cost management used to be
392
or budget management used to be one of the core expectations of project management but today
393
it's now broader to be finance performance what is the financial performance of your project
394
and that's not just how much money you're spending we're more
395
than just human calculators as project practitioners we also need to
396
take a look at the the financial equation around funding around
397
uh the the the financial equation around whether we're going to
398
generate revenue from this uh what is what is the holistic
399
financial scenario around this project not just how much did you
400
spend how much did you spend how much did you spend
401
and so i think that's going to be the most interesting evolution
402
that people will see who happen to be familiar with older versions of the Pinbox guide.
403
All right, let's open it up.
404
Here is the table of contents from the actual Pinbox guide.
405
We want to quickly review the performance domains that Jesse has mentioned.
406
Again, they're on the left and right.
407
Let me read them out for everybody.
408
2.1 at the top left there, governance performance domain, 2.2 scope performance domain,
409
2.3 schedule performance domain, and the bottom left is the finance performance domain that Jesse just mentioned.
410
Then at the top right, we have the stakeholder performance domain.
411
Below that, 2.6, the resources performance domain, and then below that, the risk performance domain is 2.7.
412
Project managers will notice that, well, several longstanding domains vanished.
413
Communication, quality, for example, they are no longer here, right?
414
Jesse, how are, I'm pretty sure you're not saying, oh, quality is no longer important.
415
We don't need to do this on a project.
416
Communication, very unimportant.
417
That's why we moved it out.
418
How are they woven into the new structure?
419
Where do we do quality?
420
How do we do communication?
421
Where's the guidance on these?
422
Well, let's talk about quality.
423
This was a hot debate.
424
I imagine.
425
This was a hot debate.
426
The seventh edition also emphasized quality as an important consideration.
427
And eventually what we came to was the conviction that we have to practice what we preach.
428
If we're saying that quality is a fundamental principle of everything we do,
429
whether it's process quality or product quality quality assurance or quality control
430
if we believe that in our bones as a fundamental principle of every project a matter approach
431
then perhaps we should embed it into the very scope of the project
432
and perhaps we should embed it into the governance of the project overall
433
and so we implemented the principle embed quality into everything you do into the document itself.
434
Yeah, right, right, right.
435
And, and, you know, I hadn't noticed that before.
436
But, you know, principle number three, embed quality into processes and deliverables.
437
There it is, right?
438
And are these seven, this is really a rhetorical question, but I have to ask it anyway,
439
are these seven domains meant to be stable for a long time? do you see them evolving as our profession evolves?
440
Well, so now you're asking me to be a bit of a fortune teller.
441
Crystal ball.
442
Yes.
443
I would say it's fair to say absolutely.
444
I think the ninth edition will have a different set of categories.
445
The same way the seventh had a different performance domains relative to the sixth's difference of knowledge areas.
446
And the sixth edition knowledge areas were different than the fifth edition, which were different than the fourth edition.
447
every edition reflects the change of the profession.
448
If we're looking for stability in what project management means,
449
look inside yourself because the world around us is changing all the time.
450
And that means that the practice is evolving all the time.
451
And the one constant that you have is you.
452
And so I'm going to be looking at me to change my techniques
453
and my skills and my approaches because the profession is changing because the marketplace is changing.
454
So I think it's fair to say that if each edition has reflected, each edition itself has had changes that reflected the changes in the marketplace.
455
I don't know about you, but just in the last year, everything has changed so much.
456
I can't even envision what's going to happen in the next four five years.
457
Yes, yes.
458
From here, we are now leaving the PMBOK guide, we're going into the back matter.
459
So we've looked at the standard, we've looked at the PMBOK guide before we head into the back matter.
460
Jesse, is there anything from your perspective
461
that you would like to add at this point to for our audience in regards to when you read this new document,
462
when you look at the the standard, when you look at the pin book, things that we should keep in mind that were very important for you and your team during the development effort.
463
I think one of the bits of feedback that we got again and again from the community was we need more examples.
464
And so this is something
465
that you'll notice in the six principles in the standard are
466
accompanied by a section called principles in action where we give
467
a concrete illustration of what it looks like to exhibit a behavioral pattern like accountable leadership
468
or uh accountable leadership likewise in the guide with the performance
469
domains there's an entire section on offering three concrete examples of how that particular arena whether it's finance performance
470
whether it's scope performance, what it looks like in actual practice.
471
So the one thing I would encourage you to do is go straight to those examples
472
because it will be more than the intent is to make it not as theoretical, but to start moving into the practical.
473
Wonderful.
474
Thank you very much.
475
And that also is a good segue into this question here.
476
We have another question about the PMP exam.
477
What about the changes in the PMP? again, does it shift the focus to memorization from situational?
478
No, no, no, no, no. Let me once again repeat, the PMP exam is not a test of the PMBOK guide.
479
Therefore, you do not need to memorize the PMBOK guide.
480
Instead, the PMP exam tests your experience as a project manager.
481
situations that every project manager sees day to day are being tested.
482
How would you react?
483
Do you understand what a normal project manager, normal project manager would do in those situations?
484
Yes, exactly.
485
Whatever a normal project manager is.
486
After all, every project is the same.
487
From here, we are moving on to the last topic from the table of content.
488
It's in the back matter.
489
And yes, everybody is interested in this right here.
490
Artificial intelligence.
491
Now, yeah, yeah, yeah, yeah.
492
And a little bit critical maybe on my side here.
493
The AI appendix, it outlines high-level use cases.
494
AI can do real-time monitoring.
495
AI can automate processes.
496
AI can identify risks and so on.
497
So there are about three, four pages of this, right?
498
Honestly, they do feel a little light.
499
They do feel maybe a little theoretical as well.
500
But is it maybe because when we look at today's project management software,
501
solid AI tools that really help us and really bring AI to the forefront of how we manage projects,
502
they are far and few in between.
503
Is that what I'm seeing here?
504
How did you work on this?
505
Or is my critique unfounded from your perspective?
506
No, I think it's a fair take on this appendix.
507
This appendix was intended to be a hyperlink to PMI's practice guides on AI.
508
So if you go onto the PMI website right now, you'll see on their landing page, a lot of resources around AI,
509
whether it's the Infinity tool set,
510
but also the practice guide for AI and project management is something that is not just available,
511
but also in development.
512
There are going to be multiple editions of this.
513
There's going to be a practice guide around how to project manage an AI project.
514
There's also going to be a practice guide about how to embed AI into project management.
515
And this appendix was intended to be a hyperlink to some
516
of the ideas to be thinking about as we start moving
517
into the AI PM world remember we started working on this two years ago uh right about
518
when chat gpt launched and
519
so what was happening is as we were evolving the the guide
520
and as we were taking community input overwhelmingly practitioners were like we need something
521
and so we felt it was appropriate to to put into the eighth edition some concepts that are fairly stable,
522
fairly universal, but the details are just so volatile.
523
You can't really put those into a standard and hope that it survives more than three months.
524
All right.
525
So that's kind of why it's a little bit ethereal and not really tangible
526
because there are other standards guidelines that are coming out and because it's such a volatile space.
527
Yeah, all right.
528
Thank you very much, especially for saying the word tangible
529
because that is much better word than my word theoretical that I use.
530
So tangible is actually, or feels a little intangible is what I should have said.
531
Yeah, okay.
532
And final question here before we begin closing out our conversation here.
533
X 3.3 there.
534
In about the middle, responsible use and ethical concerns.
535
So from your perspective, if a project manager wants to start using AI responsibly after reading this appendix X 3 here,
536
What is the very first practical step that you personally believe that they should take on Monday morning?
537
Check everything.
538
Check everything.
539
I'm working with a senior executive at a large military manufacturer
540
who is asking about the use of Microsoft Copilot inside Microsoft Project.
541
and wouldn't it be great if we could just have that available so that I can quickly re-level my integrated master schedule.
542
And so I hit a button and I'm like, make this project more efficient timeline, go.
543
And then it does some work.
544
And then you look at it, you feel, oh, fantastic.
545
It just saved me so many hours.
546
And it somehow strangely deleted 10% of my line items out of the schedule
547
because ai does that and so whatever you're using a tool
548
i have found it most helpful to get inspired by the tool on what to put into an email
549
or what the template should look like but not to just copy paste the results into my uh my next briefings
550
So buyer beware on any of the AI content that you're using.
551
It's not intended to to be a copy paste or a click and be done.
552
It's intended to be a copilot, if you will.
553
Indeed.
554
Thank you very much.
555
Which means we are moving to the close out.
556
Let's come back to my opening statement.
557
So you think you know what a product is?
558
Think again.
559
And here we want to take a look at the updated modern definitions.
560
Two of them, in fact.
561
First of all, this is what a project is.
562
A project is a temporary initiative in a unique context undertaken to create value.
563
This new definition, crisp, compact.
564
What misconceptions about projects were you trying to resolve with this wording?
565
So if you go back to the previous definition,
566
this is a temporary endeavor undertaken to create a unique project service or result.
567
Exactly.
568
That definition is 40 years old.
569
It has not changed since the PMI first started thinking of what a body of knowledge would look like
570
or a codification of practice would look like.
571
And if you think about the terminology at the time,
572
a unique product, service, or result is focusing on the thing.
573
It's focusing on the deliverable, not on the value proposition that the deliverable supports.
574
And so what happens a lot of times on projects is that there'll be a pivot.
575
there'll be a fundamental change request that comes in and says, you know what, we need to chop off this part of the scope in favor of this part of the scope.
576
Or we've just blown through our schedule, we need to rethink the value proposition.
577
And does that mean now that the unique product service or result is obsolete?
578
Sometimes it does.
579
Instead, the value proposition now needs to be served by a different product or a different service or a different result.
580
This also, this re-examining of definitions came independently of the project success research
581
that PMI was doing to define what project success was, which is whether it's considered worth it.
582
And so we were challenged as a team to think, it's been 40 years.
583
Should we be rethinking what fundamentally the project is about?
584
And projects are not about the thing.
585
They're about the why behind the thing that we're building.
586
All right.
587
Thank you very much.
588
I would like to bring up another misconception here that I need to clear up.
589
Does the current PMP exam question refer to version eight concepts?
590
No, they do not.
591
The new PMP exam is going to be launched in July of 2026.
592
Until that time, you do not need to worry really about PMBOK 8.
593
It'll help, but it, you know, you don't really need to worry about it.
594
Final slide here.
595
We are moving on from the definition of project to the definition of project management,
596
which is now the application of knowledge,
597
skills, tools and techniques to project activities to meet or exceed the intended value.
598
Once again, this definition puts the intended value at the finish line.
599
How then would that influence how we define the scope, how we plan, how we lead?
600
What's your insight here that you can share with us?
601
Yeah, the original definition for project management at the same time as that definition of project came out in the 1986 pre-PIMBOK,
602
called out that the definition of project management was application of knowledge,
603
skills, and tools to meet or exceed project stakeholder expectations.
604
And then somewhere along the way, our community said, no, no, no, no. It's about the requirements.
605
And so the definition of project over the recent 10 to 15 years has been about satisfying project requirements.
606
What if the requirements are wrong?
607
and and and and guess what project manager that's your job your job is to make sure
608
that the project requirements capture some kind of a business case
609
some kind of a value proposition in order to move forward um
610
so i'm about to audit a very large it project right now where there's one executive
611
that says the requirements are the definition of success i'm not
612
going to pay for anything more I'm not going to tolerate any further delays, the requirements.
613
But then there's another executive in a different department.
614
They're both peers who says, but I won't be able to use it.
615
Now, the one who wants to use it is not the one paying for it.
616
It's the other executive.
617
And so now they get to have an executive cage match.
618
Go fight it over.
619
I'm the project manager.
620
All I did was reveal you have a fundamental misalignment on what the success of a project is.
621
And it's my job not to solve that but to make sure
622
that it gets solved by the appropriate players that's what project
623
management is it's not complying to requirements it's meeting expectations of
624
what the value proposition is about wonderful thank you very much with
625
that we have come to the end of our conversation here
626
on the pinball guide eighth edition we looked at the standard we looked at the PMBOK Guide.
627
And third, we looked a little bit at the back matter there with AI.
628
Before I say thank you very much, let's let people know where they can get their copy of the PMBOK Guide.
629
I bought mine at the Global Summit, you probably got one for free, I hope, for all the work that you've put into this.
630
Where can our audience get the PMBOK Guide?
631
So if you just go to PMI's website and look under the standards section, and it is the flagship standard,
632
it'll be right there for free download to anyone who is a PMI member in good standing.
633
Not merely a certification holder, but if you are a paying member in good standing with an annual membership that comes renewal each year,
634
it's a free download.
635
PDF.
636
Go for it.
637
If you want a hard copy,
638
then you can pre-order your print copy today to be shipped to your home in January.
639
The full print run is going to be happening over the holidays.
640
So just go to PMI's website
641
and you'll be able to take a look either for your free member download
642
or a paper copy or a non-member digital copy for purchase.
643
Right.
644
And I think if you want it in a language other than English, you have to wait until April, if I remember the date correctly.
645
Right.
646
That sounds right.
647
The translations are underway and will be released in the middle of 2026.
648
All right.
649
Jesse, thank you so much for being here.
650
It's only been a little over a week since PMBOK 8 has been released.
651
I really appreciate your flexibility to come on here and bring the new Pimbockeye to our audience.
652
It's been my pleasure.
653
Absolute treat.
654
And for those of you who want to talk about this more, feel free to reach out to me on LinkedIn.
655
I have a personal policy of accepting any invite from any project practitioner.
656
Would love to continue the conversation.
657
Right.
658
I will put your LinkedIn profile link into the show notes of this episode here,
659
which is episode 542 of the Project Management Podcast.
660
Once again, Jesse, thank you very much.
661
Thank you, Cornelius.
662
All the best.
663
All right.
664
Thank you, everybody.
665
Please do visit pm-podcast.com slash 542 for the show notes and also for Jesse's LinkedIn profile link.
666
You can claim PDUs for participating, watching, listening to this episode.
667
Looks like about 0.75 PDUs in ways of working.
668
And our email address is info at pm-podcast.com.
669
And finally, we have this here, the Galaxy Brain Meme, which should have been animated, but it isn't.
670
So let me walk you through it.
671
At the top left, the first brain is when you're thinking that, yeah, Pimboc 8, that's just Pimboc 7 with new lipstick.
672
Below that, the second brain, a little bit more active when you realize, oh my, the principles have changed.
673
Then at the top right, your brain is getting more activity going.
674
You're realizing the domains have changed.
675
And lastly, at the bottom right, your brain is exploding because you realize even the definition of the term project has changed.
676
And with that, I bid you farewell.
677
Until next time.
アプリをダウンロード
流暢に話すために必要なすべて
AI発音採点文ごとに採点
IPA練習すべての音をマスター
単語学習自分の単語帳を作る
単語ゲーム遊びながら覚える
FOR YOU
おすすめ動画
C1240 文
PMBOK 8th Edition Practice Questions 1 - 10 - Pass your PMP and Learn the PMBOK Guide
Business EnglishWorking Adults
C11
527 文
Trade, tech and geopolitics: what you need to understand about China today
Business EnglishDaily ConversationUniversity Students
C12
210 文
What Software Architecture Should Look Like • Dave Farley • GOTO 2022
Business EnglishUniversity StudentsWorking Adults
C14
206 文
New Skills! v1.1 brings /wayfinder, /research, /implement, /to-spec, /to-tickets
British AccentBusiness EnglishUniversity StudentsWorking Adults
C11
689 文
Natural Stone 101: Everything You Need to Know About Designing with the Oldest Building Material
Business EnglishUniversity StudentsWorking Adults
B27
292 文
Let's talk About How to Stop Procrastinating and Take Action Today - Speak Power Daily Podcast
Business EnglishDaily ConversationUniversity Students
C12
494 文
Everything we learned in 29 minutes at Harvard Business School (part 1)
Business EnglishUniversity StudentsWorking Adults
C12
213 文
The Technical, Business and UX Skills Every Product Manager Needs
Business EnglishUniversity StudentsWorking Adults
C13
356 文
#02 Common Pitfalls of building Human Resources Strategies
Business EnglishUniversity StudentsWorking Adults
B21012 文
Project Management English — Key Terms and 7 Real Meetings | Business English Podcast
Business EnglishWorking Adults
C13
260 文
【TED】優れたリーダーはどうやって行動を促すか/サイモン・シネック （日本語字幕）
Business EnglishDaily ConversationUniversity Students
B21
435 文
Don't Lose the Room: How to Make Ideas Stick
Business EnglishDaily ConversationUniversity Students
このレッスンについて
このレッスンでは、「PMBOK Guide 8版」についてのビデオを使って、英語のリスニングとスピーキングを練習します。プロジェクトマネジメントの専門用語や、自然な会話の流れ、発音の特徴を観察しながら、動画で英語学習の楽しさを体験しましょう。特に、shadow speak（シャドーイング）の技法を使って、話者のリズムやイントネーションを真似る練習がポイントです。
重要な語彙とフレーズ
- PMBOK Guide：プロジェクトマネジメントの国際標準ガイド
- foundational concepts：基本的な概念
- renewal cycle：更新周期
- "It is a deliberate move towards..."：「...への意図的な移行です」（論理的な説明に使える表現）
- "I need to get off my chest"：「胸中を晴らしたい」（率直な意見を述べる時の口調）
練習のヒント
このビデオの会話は自然なスピードで、専門用語も含まれますが、英語シャドーイングの際はまずリズムを捉えることから始めましょう。話者が「Well, think again.」のように軽く語気を入れる部分や、「Thank you so much for joining us」のような丁寧な表現のイントネーションを真似ると、shadowspeakの技術が上達します。また、IELTS スピーキング対策にも役立つ論理的な会話の展開を観察し、自分で同じ内容をまとめて話す練習を加えると効果的です。何度も繰り返し聞き、少しずつスピードを上げながら挑戦してみてください。
この動画の文法
話し手がよく使っている文型を、動画の実際の表現とともに紹介します。
| 文型 | 動画での表現 |
|---|---|
| 現在完了進行形 have/has been + -ing — 以前に始まり今も続いている動作 | that's been evolving · have been promoting · have already been working |
| 「used to」 used to + 動詞 — 今はもう違う過去の習慣や状態 | used to be |
| 現在完了形 have/has + 過去分詞 — 過去の出来事が今も関係している | has dropped · has coached · has been |
| 受動態 be + 過去分詞 — 誰がするかより、何が起きるかに焦点を当てる | is built · were set · is required |
シャドーイングとは？英語上達に効果的な理由
シャドーイング（Shadowing）は、もともとプロの通訳者養成プログラムで開発された言語学習法で、多言語習得者として知られるDr. Alexander Arguelles によって広く普及されました。方法はシンプルですが非常に効果的：ネイティブスピーカーの英語を聞きながら、1〜2秒の遅延で声に出してすぐに繰り返す——まるで「影（shadow）」のように話者を追いかけます。文法ドリルや受動的なリスニングと異なり、シャドーイングは脳と口の筋肉が同時にリアルタイムで英語を処理・再現することを強制します。研究により、発音精度、抑揚、リズム、連音、リスニング力、そして会話の流暢さが大幅に向上することが確認されています。IELTSスピーキング対策や自然な英語コミュニケーションを目指す方に特におすすめです。