Jo Ann NoelProject Manager| Ministry of PlanningEl Dorado, Trinidad and Tobago
Only when necessary. I referenced from time to time. Saving Changes...
Karen HaefnerSenior Manager, Marketing Communications Program Management| K&L GatesBethel Park, Pa, United States
Never. It's like a manual that comes with a new appliance. You file it away because you think you might need it some day, but if/when you experience a problem you do an internet search or talk to people you know for advice. You never go looking for that manual. Saving Changes...
Dear Senthil, thank you for the thoughtful question.
As a novice lacking of practical opportunities and in-depth experience, I often refer to PMBOK and organization knowledge books to learn and apply. Saving Changes...
When I first became a project manager, I'd use it every few weeks but now I refer to it when I'm wanting to clarify a specific definition or concept. I do like reading the newer versions to see what's new Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Nov 06, 2019 4:21 AM
Replying to Sergio Luis Conte
...
Not at all. Wehen the process is created you do not need to review it against the PMBOK Guide. You need to review it in terms of the reality. On the other side PMBOK Guide is just that, a guide. We use things that are not part of the PMBOK Guide. At least that is the approach I have used from long time ago due to I am in charge of all related to process creation and implementation in the work places were I have the pleasure to work.
Dear Sergio
Do you usually review project management processes as a result of the new editions of PMBOK Guide?
...
1 reply by Sergio Luis Conte
Nov 10, 2019 9:44 AM
Sergio Luis Conte
...
I am part of the group of authors and reviewers of all PMI´s standards. I do that because is the mean to contribute to the profession and to be updated myself. I am doing that from 2010. No matter that, what I teached and I have used from long time ago (1990 up to date) when I helped organizations to implement project management in the PMI way is this: the important things are the knowledge area. Second, the process that could help to define the functions/process the organization have to implement to address its strategy. Tools and techniques, forget about it generally speaking. With that said, as you notice, the "big changes" in PMBOK from 2000 up to date are the process named but nothing about the basement. It does mean that everything is invented in project management. For that reason, in my personal opinion, PMI is trying to keep the business run by experienced new ways on do that. For example, because the last Agile guide was software focused, now PMI is trying to change the focus. Or other thing like Benefit Relationship Management. So, nothing to review in scence mainly becuase as its name stated is a guide, not a "bible".
Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Nov 10, 2019 7:52 AM
Replying to Luis Branco
...
Dear Sergio
Do you usually review project management processes as a result of the new editions of PMBOK Guide?
I am part of the group of authors and reviewers of all PMI´s standards. I do that because is the mean to contribute to the profession and to be updated myself. I am doing that from 2010. No matter that, what I teached and I have used from long time ago (1990 up to date) when I helped organizations to implement project management in the PMI way is this: the important things are the knowledge area. Second, the process that could help to define the functions/process the organization have to implement to address its strategy. Tools and techniques, forget about it generally speaking. With that said, as you notice, the "big changes" in PMBOK from 2000 up to date are the process named but nothing about the basement. It does mean that everything is invented in project management. For that reason, in my personal opinion, PMI is trying to keep the business run by experienced new ways on do that. For example, because the last Agile guide was software focused, now PMI is trying to change the focus. Or other thing like Benefit Relationship Management. So, nothing to review in scence mainly becuase as its name stated is a guide, not a "bible".
...
1 reply by Luis Branco
Nov 10, 2019 4:16 PM
Luis Branco
...
Dear Sergio
Very important this your comment.
I didn't know that you belong to the group of authors and reviewers of all PMI's standards.
I can only congratulate you on that.
We agree that what matters is the knowledge areas
We still agree that processes (processes + knowledge areas) have to be used by organizations to adress its strategy
Some techniques and tools may also be helpful (I take the opportunity to tell you that removing the 7 habits of highly effective people and the 8 habit as a reference for leadership, instead proposing emotional intelligence and servant leadership went backwards)
After this explanation, which I thank you very much, it occurs to me to ask you:
Do you bring to PMBOK Guide your knowledge related to your company's process management reviews?
Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
As needed, as a reference should be, though, in the past couple years, certainly less and less frequent to the point of pretty much nil.
...
1 reply by Luis Branco
Nov 10, 2019 4:24 PM
Luis Branco
...
Dear Andrew
Interesting your comment
In this sixth edition the PMBOK Guide introduced (with more emphasis):
- Adaptive approaches (predictive, iterative and agile) - Tailoring
- Trends in the business environment
Which allows us to change the paradigm in the project development approach
After reading Sérgio's comment, I believe PMI is chasing the loss (where you can integrate the logo change :-))
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Nov 10, 2019 9:44 AM
Replying to Sergio Luis Conte
...
I am part of the group of authors and reviewers of all PMI´s standards. I do that because is the mean to contribute to the profession and to be updated myself. I am doing that from 2010. No matter that, what I teached and I have used from long time ago (1990 up to date) when I helped organizations to implement project management in the PMI way is this: the important things are the knowledge area. Second, the process that could help to define the functions/process the organization have to implement to address its strategy. Tools and techniques, forget about it generally speaking. With that said, as you notice, the "big changes" in PMBOK from 2000 up to date are the process named but nothing about the basement. It does mean that everything is invented in project management. For that reason, in my personal opinion, PMI is trying to keep the business run by experienced new ways on do that. For example, because the last Agile guide was software focused, now PMI is trying to change the focus. Or other thing like Benefit Relationship Management. So, nothing to review in scence mainly becuase as its name stated is a guide, not a "bible".
Dear Sergio
Very important this your comment.
I didn't know that you belong to the group of authors and reviewers of all PMI's standards.
I can only congratulate you on that.
We agree that what matters is the knowledge areas
We still agree that processes (processes + knowledge areas) have to be used by organizations to adress its strategy
Some techniques and tools may also be helpful (I take the opportunity to tell you that removing the 7 habits of highly effective people and the 8 habit as a reference for leadership, instead proposing emotional intelligence and servant leadership went backwards)
After this explanation, which I thank you very much, it occurs to me to ask you:
Do you bring to PMBOK Guide your knowledge related to your company's process management reviews?
...
1 reply by Sergio Luis Conte
Nov 10, 2019 4:52 PM
Sergio Luis Conte
...
Hi Luis. My reference about I am part of the group is just to give some context. As you know is a position as voluntary and everybody can apply. The PMI has a process to evaluate applications that is "rigorous" but I think it could be good that each person who think valuable to apply take the option. Just to remember and encourage people to participate beyond the initial process is the option to participate as reviewer when the draft is published. About your last question, I think people that participate put the practical experience into each proposal to include/change something inside the PMBOK. In my case, beyond my experience, as a hobby I am researching about most of the topics included as knowledge areas and I tried to put the academic research on practice so my participation on the groups of authors/reviewers in the standards is driven for that situation. I am trying to maintain the abstraction when I make my comments due to PMI´s standards have to be not specific for a domain.
Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Nov 10, 2019 1:04 PM
Replying to Drew Craig
...
As needed, as a reference should be, though, in the past couple years, certainly less and less frequent to the point of pretty much nil.
Dear Andrew
Interesting your comment
In this sixth edition the PMBOK Guide introduced (with more emphasis):
- Adaptive approaches (predictive, iterative and agile) - Tailoring
- Trends in the business environment
Which allows us to change the paradigm in the project development approach
After reading Sérgio's comment, I believe PMI is chasing the loss (where you can integrate the logo change :-))
...
1 reply by Drew Craig
Nov 10, 2019 6:38 PM
Drew Craig
...
My career has shifted over the last few years, and now, while still under PPM, in management consulting side over delivery. I tend towards other sources of documentation these days, though still a big proponent of the direction of PMI.
Nonetheless, that's why we have a bookshelf of various references - for just that one occasion!