If I had to pick one, I would say 9.4 Develop Team on occasion is not necessary. The reason is that some teams are already mature and basically only need to be managed moreso than developed. The output of 9.4 Develop Team which is "Team performance assessment" could be performed during 9.5 Manage Team in the above context. Saving Changes...
Agreed, if you are with a long-lived team which has just moved from one project to the next, that process might be minimal.
As with everything else in the PMBOK Guide, process utilization will scale based on the needs of the project. For example, many of the projects I worked on earlier in my career were software development projects using internal staff only and hence there was no need for the full Procurement Management knowledge area!
Of course, in some companies, the lack of performing a given process might actually be reflective of low organizational PM maturity - I've seen my fair share of companies whose quality management practices extend solely to QC...
Kiron
...
1 reply by Sante Delle-Vergini, PhD
Mar 19, 2018 7:02 AM
Sante Delle-Vergini, PhD
...
Yes, other than an initial make or buy analysis in certain cases, some projects would need little if any of the procurement management knowledge area.
Agreed, if you are with a long-lived team which has just moved from one project to the next, that process might be minimal.
As with everything else in the PMBOK Guide, process utilization will scale based on the needs of the project. For example, many of the projects I worked on earlier in my career were software development projects using internal staff only and hence there was no need for the full Procurement Management knowledge area!
Of course, in some companies, the lack of performing a given process might actually be reflective of low organizational PM maturity - I've seen my fair share of companies whose quality management practices extend solely to QC...
Kiron
Yes, other than an initial make or buy analysis in certain cases, some projects would need little if any of the procurement management knowledge area. Saving Changes...
Hi Sante, I agree with you as well, but there was one time only where I used it and in details,
I was given a very inexperienced team and that all that the company had. I had to develop the team from scratch with no other choice.
...
1 reply by Sante Delle-Vergini, PhD
Mar 19, 2018 9:13 AM
Sante Delle-Vergini, PhD
...
Kevin, sure there are many times when we certainly need to develop the team.
Hi Sante, I agree with you as well, but there was one time only where I used it and in details,
I was given a very inexperienced team and that all that the company had. I had to develop the team from scratch with no other choice.
Kevin, sure there are many times when we certainly need to develop the team. Saving Changes...
I have yet to read PMBOK 6, I keep using v5 since all my annotations are there and it can be put in the v6 PDF (lock) for PMI member!
I would agree that Develop team is important, but in many case the team is moving from one project to the next.
Ah ok Vincent. Well the same questions can apply to version 5 also :-) Saving Changes...
Delrose BrownVice President - Business Leader - Product Delivery| Mastercard CanadaBrampton, Ontario, Canada
To me, the 6 Process Groups are all useful. Of the 47 processes, I believe Manage Communication & Manage Stakeholder Engagement should be combined. In fact, the knowledge areas for Stakeholder and Communications should be combined :-)
...
2 replies by Dinah Young and Sante Delle-Vergini, PhD
Mar 19, 2018 2:17 PM
Dinah Young
...
I agree. Those two areas tripped me up a few times. They overlap so much that it may be better to combine them.
Mar 19, 2018 10:38 PM
Sante Delle-Vergini, PhD
...
That's an interesting thought Delrose.
Saving Changes...
Dinah YoungProject Manager / Software Asset Manager| Prince William CountySpringfield, Va, United States
Mar 19, 2018 12:24 PM
Replying to Delrose Brown
...
To me, the 6 Process Groups are all useful. Of the 47 processes, I believe Manage Communication & Manage Stakeholder Engagement should be combined. In fact, the knowledge areas for Stakeholder and Communications should be combined :-)
I agree. Those two areas tripped me up a few times. They overlap so much that it may be better to combine them.
...
1 reply by Kiron Bondale
Mar 19, 2018 2:28 PM
Kiron Bondale
...
When they were combined (PMBOK 4th edition and before), stakeholder management was somewhat marginalized...
"There is a theory which states that if ever anybody discovers exactly what the Universe is for and why it is here, it will instantly disappear and be replaced by something even more bizarre and inexplicable.
There is another theory which states that this has already happened."
