It's true most of what we implement in projects are based on theory, such as the PMBOK guide for example. However, not everything can be put into practice in exactly the same way as what the theory says. Which are some aspects of the project in which you experienced this? Saving Changes...
This is true of every project aspect given the uniqueness of a project's context trumps any framework's guidance. Principles are universal whereas practices, tools, processes and roles are context-dependent.
A simple example is the use of a WBS. In some projects it can be a critical, valuable PM artifact whereas in others it would be a waste of effort.
Kiron
...
1 reply by Bisharah Saeed
Dec 04, 2024 4:02 AM
Bisharah Saeed
...
Exactly Kiron. I agree that the context plays an important role. Like you said, the WBS makes much more sense when we have detailed information or when the project is quite huge, however in a small project, it wouldn't make that much sense.
This is true of every project aspect given the uniqueness of a project's context trumps any framework's guidance. Principles are universal whereas practices, tools, processes and roles are context-dependent.
A simple example is the use of a WBS. In some projects it can be a critical, valuable PM artifact whereas in others it would be a waste of effort.
Kiron
Exactly Kiron. I agree that the context plays an important role. Like you said, the WBS makes much more sense when we have detailed information or when the project is quite huge, however in a small project, it wouldn't make that much sense. Saving Changes...
From my point of view, the maturity of the organization is the most important influencing factir to consider. You cannot "throw" the entire PMBOK at an organization with a very low maturity in project management. You might be forced to do project work in Excel and continously explaining what "matrix organization" and "committed resources" means...
...
1 reply by Bisharah Saeed
Dec 04, 2024 2:55 PM
Bisharah Saeed
...
Thanks for sharing your input Svenja! That matters a lot too! Sometimes firms just don't want to shift and that makes lives harder for project managers.
PMBOK provides the structure and framework needed to analyze situations and take effective actions. A stronger structure leads to better actions and, ultimately, better results.
...
1 reply by Bisharah Saeed
Dec 04, 2024 2:56 PM
Bisharah Saeed
...
Thanks for sharing your input. Sure, definitely the PMBOK leads to a stronger structure but can that be possible in all situations? Sometimes experience teaches us better ways to deal with situations.
From my point of view, the maturity of the organization is the most important influencing factir to consider. You cannot "throw" the entire PMBOK at an organization with a very low maturity in project management. You might be forced to do project work in Excel and continously explaining what "matrix organization" and "committed resources" means...
Thanks for sharing your input Svenja! That matters a lot too! Sometimes firms just don't want to shift and that makes lives harder for project managers. Saving Changes...
PMBOK provides the structure and framework needed to analyze situations and take effective actions. A stronger structure leads to better actions and, ultimately, better results.
Thanks for sharing your input. Sure, definitely the PMBOK leads to a stronger structure but can that be possible in all situations? Sometimes experience teaches us better ways to deal with situations. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
With all my due respect, I do not agree with you in "such as the PMBOK guide". By definition of a BOK (PMBOK, BABOK, SWBOK, etc etc) means you only have there a list of things that have been proved in the practice could help to achieve the objectives. But here is the key. "every house is a world". To put this in terms of PMI you can find answers on the matter in related documentation about business analyst role. Saving Changes...