Project Management

Please login or join to subscribe to this thread

Which knowledge area is important yet often neglected (or least prioritized)?

linkedin twitter facebook   Organizational Project Management  
avatar
Venkata Rama Satish Nyayapati Hyderabad, Telangana, India
Which knowledge area is important for the success of the project, yet most often neglected (or least prioritized/least time spent on it)?
Share your thoughts/experiences.
Sort By:
< 1 2 >
avatar
Mohammad Sulaiman Al-Yuzbashi PM Consultant| Devoteam Riyadh, Saudi Arabia
Thanks everybody for your input and allow me to add my two pennies on the subject.

First I would disagree with most of the gentlemen and ladies when I say that you are allowed, as a PM, to "neglect" any process/process group/knowledge area within the context of your project if you deem them as expendable to that project. PMBOK is, and I'm improvising here, a repository of what is globally accepted as best-practices in the domain of project management in the form of processes (inputs, tools & techniques, outputs) and project managers has the freedom to use all the processes that they feel will increase the probability of delivering their projects successfully and to leave the rest of the field unused.

After saying that, I would say that the processes of the "Stakeholders Management" knowledge area is the least used among the the processes described in the PMBOK due, to my opinion, to:
A) being the latest addition in the Sixth Edition.
B) the implied secrecy associated with the Stakeholders Register, the main product of the processes within this knowledge area, which usually prevent it from being formalized.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Do not fear to be eccentric in opinion, for every opinion now accepted was once eccentric."

- Bertrand Russell

ADVERTISEMENT

Sponsors