Project Management

Project Management Central

Please login or join to subscribe to this thread

Topics: Estimating, Using PMI Standards
Which PMBOK tool or technique do you find to be the most versatile?
Whether it is studying for the PMP or CAPM exams or just browsing the PMBOK Guide to stay current as it has evolved, you will learn about hundreds of different hard and soft tools & techniques which could be used (context-depending, of course).

But is there one which you've found is the "Swiss Army Knife" in your toolbox?

I've found the Wideband Delphi technique to be extremely versatile - whether it is for estimating, assessing risk probabilities & impacts or for almost any other type of group decision making, it has proven to be very useful.
Sort By:

The Delphi technique is also one that has caught my fancy.I read it is particularly suitable for the scenario depicted in the question:

" You are newly appointed as PM for XYZ Inc., and after one week, you observed Jason a team member exercising undue influence on the project.You are considering the best option to take for activity and cost estimation"

Please take note the main concern of the PM here is how to minimize Jason's undue influence as per which T& T can best be used to dampen Jason's undue influence.
I use one not in the PMBOK called an N-Squared or NxN diagram. It is like many matrices which show the intersection of 2 things, but it also shows the direction of information flow. I learned this for interface management in satellite design and then started seeing project teams as systems of people, processes and tools where I could apply it as well.

In engineering systems, clusters of interfaces between physical items on the chart become natural modules. With people it makes natural sub-teams. I can put a big grid on a war-room wall and use it for SOW development asking each team, "Do you need anything from Group X?", and mark it on the chart until we think we've captured all our data exchanges between teams. I can color code them for a tracking tool where Red = identified, Yellow = scheduled and Green = complete. That gives me a great visual heat map. It is also scaleable where a module or sub-team can be broken down into its own detail level diagram.

I've found all kinds of ways to use it and very simply document the flow of information, and show where the most critical information flow occurs, both as a development tool and a management tool.
Like Keith. I use a tool and technique outside of the PMBOK that is called Johari Window Map. It is very interesting and can be versatile.

Please login or join to reply

Content ID:

"If you have an apple and I have an apple and we exchange apples then you and I will still each have one apple. But if you have an idea and I have an idea and we exchange these ideas, then each of us will have two ideas."

- George Bernard Shaw