I have been a project management team member and recently gained my PMP Certification. I feel overwhelmed by all of the tools and techniques listed in the PMBOK Guide, I need guidance. Thank you. Saving Changes...
I would like to better understand your question "I feel overwhelmed by all the tools and techniques listed in the PMBOK Guide, I need guidance"
Can it be a little more specific?
Dear Luis,
My question states how to use "All or Most" of the project management tools, techniques, process, and practices while being constrained by following specific ones in the organisation. In other words, how to experience and experiment those stated in the PMBOK guide in order to gain more experience and lessons learnt?
Like any good professional, an effective PM has a deep and wide toolkit but knows which tools to use in what situations.
Context counts which is why domain expertise is valued along with PM hard & soft skills competency.
I'd suggest finding yourself an (in person) mentor in the company where you currently work as they can coach you in the use of the right tools in the right contexts.
I can’t agree more with Kiron’s feedback, it’s spot on. To apply theory, you need experience in order to know how to customize the processes, tools and techniques to suit your project needs.
RK
I couldn't agree more, Rami.
Thanks. Saving Changes...
As the name stated is a guide. You must select the tools and techniques that best fit for your situation or you can not use anything of them for some knowledge area as I do in my actual work place. What I saw along the years is difficult not to take into account all the knowledge areas but regarding process/tools/techniques stated inside them you can discard a lot.
Thanks for sharing, Sergio.
...
1 reply by Sergio Luis Conte
Jan 05, 2020 3:06 PM
Sergio Luis Conte
...
You are welcome. The best source I found along the years just talking about a book is: "Visualizing Project Management: Models and Frameworks for Mastering Complex Systems" writting by Kevin Forsberg (Author), Hal Mooz (Author), Howard Cotterman (Author). This is a mostly forgotten book and is chiper than others but it is a must read mainly because is based on V life cycle which is one of the first Agile based life cycles that were created (and I was part of it..jejejeje, as moch others). Just in case you need something mostly used on Agile the best book is "Agile Estimating and Planning" written by Mike Cohn. It will give you tools and techniques do not stated into the PMBOK which could or not used inside Agile based environment. And just in case you are inside waterfall based environements and you need to apply Agile in there go for Tom Gilb work called EVO and forget something else.
a. Consider the Org. structure (your authority/power)
b. Historical Knowledge (previous project, current processes, and evolving policies)
c. Templates (don't reinvent the wheel)
d. Experienced "internal" PM's (learn-from / lean-on others)
e. Relax (you were hired for a reason)
A good point you bring up about how to apply our theoretical knowledge to project management when a lot of the time we are following others peoples tools, techniques, templates, methodologies and approaches and merely adding our own flavour to the project and applying our experience to the leadership of the project. There are many approaches and tools that may work in theory but we do not have the time, resources and sometimes vision in order to see if they would work in the project management office. It would be great if PMI had a sort of PMO lab either virtually or physical where as project manager we could apply some of our lessons learned from a project in cold environment instead of trying to implement it hot on a actually project.
Daire
Daire,
Thank you for your insightful point of view and brilliant suggestion. Saving Changes...
The best way to try out some of the PM tools that dont exist in your organisation is to do exactly that ,try them out. Pick a small project you are working with and try out one of the techniques you think will work. Many years ago I tried the 3 point estimate out with a small project I was working on, the team and the organisation was maturing to PM techniques so it was a welcomed experiment. It took more time to build the schedule but the result was a schedule that people had spent time developing and thinking about in terms of the pessimistic and optimistic and most likely effort estimates, became a "realistic" estimate. The spin-off of the process was identifying more risks. Also, try and make the process of implementing tools and techniques fun for the team so you have their buy-in in the process. All the best. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Jan 05, 2020 12:47 PM
Replying to Zaid Al-Matari
...
Thanks for sharing, Sergio.
You are welcome. The best source I found along the years just talking about a book is: "Visualizing Project Management: Models and Frameworks for Mastering Complex Systems" writting by Kevin Forsberg (Author), Hal Mooz (Author), Howard Cotterman (Author). This is a mostly forgotten book and is chiper than others but it is a must read mainly because is based on V life cycle which is one of the first Agile based life cycles that were created (and I was part of it..jejejeje, as moch others). Just in case you need something mostly used on Agile the best book is "Agile Estimating and Planning" written by Mike Cohn. It will give you tools and techniques do not stated into the PMBOK which could or not used inside Agile based environment. And just in case you are inside waterfall based environements and you need to apply Agile in there go for Tom Gilb work called EVO and forget something else. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Zaid,
I concur with what was said.
In my own words,
- PMBoK is a Guide and it requires 'tailoring' of its content to each organization (e.g. by a PMO as a company standard PM handbook) and further to each project (to the project management plan). There is a tailoring appendix in PMBoK and hints in each knowledge area what to look for when tailoring.
- I have seen several new PMPs frustrated when they try to apply most of PMBoK to their business environment, because colleagues and managers thought it is too big, too much, too complicated, buerocratic and not proven in the specific situation. They are right.
- The knowledge is now in your head, it is primarily your asset and you have to select it bit by bit and gain experience with it. This can take years. Not every project is suitable for this. At least you now know the structure and base principles. Saving Changes...
