Project Management

Please login or join to subscribe to this thread

Another "head-tipper" in version 6

linkedin twitter facebook  
avatar
David Maynard Fort Wayne, In, United States
In chapter 4, (page 73) under "TRENDS AND EMERGING PRACTICES IN PROJECT INTEGRATION MANAGEMENT" in the bullet list (fourth bullet) "Project knowledge management"

It mentions that because of an "increasingly mobile and transitory work force" it's required that we have a *more* rigorous process of identifying knowledge throughout the project life cycle and transferring it to the *target audience* so that the knowledge is not lost.

Who is this "target audience"? That's a new term in the guide to me. Is this the stakeholders? Maybe it's the "mobile and transitory work force" or maybe it's someone else?

Also, what areas of identifying knowledge should be made more rigorous when we have a mobile workforce?
Sort By:
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
David -

it depends on the nature of the knowledge captured. The dispersed/distributed folks could both be sources of new knowledge but might also need to receive the newfound knowledge. However, there are likely stakeholders outside of these folks who would need to receive the knowledge, hence the generic term.

Kiron
avatar
David Maynard Fort Wayne, In, United States
Does version 6 support the version 5 concept of a negative stakeholder -- one that doesn't really want the project to succeed? In version 5, the concept of a "negative" stakeholder was introduced near the end of section 2.2.1 Project Stakeholders..

"The project team identifies internal and external, positive and negative, and performing and advising stakeholders in order to determine the project requirements and the expectations of all parties involved. The project manager should manage the influences of these various stakeholders in relation to the project requirements to ensure a successful outcome.:
...
1 reply by Kiron Bondale
May 18, 2018 7:50 AM
Kiron Bondale
...
David -

The attitude of stakeholders is referenced in section 13.2.2.5 where they cover the Stakeholder engagement assessment matrix.

Unlike risks, where a layperson would assume they are always threats, most folks are comfortable with the concept of stakeholders being for, against or neutral about the project so there wasn't the need to emphasize this.

Kiron
avatar
Sergio Luis Conte Helping to create solutions for everyone| Worldwide based Organizations Buenos Aires, Argentina
You have to go to knowledge management literature to have your answers. You will find that PMBOK is talking about things like knowledge management base.All that is included in the context of 4.4.Manage Project Knowledge where you can find Knowledge Management as a tool.
avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
May 17, 2018 4:23 PM
Replying to David Maynard
...
Does version 6 support the version 5 concept of a negative stakeholder -- one that doesn't really want the project to succeed? In version 5, the concept of a "negative" stakeholder was introduced near the end of section 2.2.1 Project Stakeholders..

"The project team identifies internal and external, positive and negative, and performing and advising stakeholders in order to determine the project requirements and the expectations of all parties involved. The project manager should manage the influences of these various stakeholders in relation to the project requirements to ensure a successful outcome.:
David -

The attitude of stakeholders is referenced in section 13.2.2.5 where they cover the Stakeholder engagement assessment matrix.

Unlike risks, where a layperson would assume they are always threats, most folks are comfortable with the concept of stakeholders being for, against or neutral about the project so there wasn't the need to emphasize this.

Kiron
avatar
Margaret Love Senior Instructor| Velociteach Greenville, Sc, United States
I agree with all answers above. I would add that many projects now seem to be managed by consultant PM's, and as consulting PM's we have to not only manage the project well but also be sure that the people we are working for are left with the knowledge of how we did it. This puts emphasis on knowledge transfer along the way - explaining why, properly storing things, making our work visible, etc. - and also on proper close-down when we leave. "Back in the day" when projects were mostly managed in-house, the PM would be around to ask how we did this or that. But that's no longer the case for many projects. So I would add to the comments that the "target audience" is the customer you are working for if you are a consulting PM.
(And by the way... the same is true for ALL project consultants - they have to be diligent about knowledge transfer in their particular area.)

Please login or join to reply

Content ID:
ADVERTISEMENTS

"The amount of money one needs is terrifying..."

- Ludwig Van Beethoven

ADVERTISEMENT

Sponsors







Vendor Events

See all Vendor Events

Newsletters

Jun 3: The Career Problem Facing New PMs
May 20: Your PM Career as a Project Life Cycle
May 13: The Big Lie After Layoffs

See all newsletters