I have been requested to develope a Project management framework. How would I structure my framework. Need advise. Thanks on the
Chris OrohoSenior Internal Auditor| National Fisheries AuthorityPort Moresby, Ncd, Papua New Guinea
I have been requested to develop a Project Management Framework for my organisation. How can I structure my framework and what would the contents of my framework be? Thanks. Saving Changes...
Sort By:
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Key thing is to understand what a framework is. Is like a MS Word template for example. You have the main structure and you have to fill it up with the techniques and methods that best fits for each initiative and the environment. For example, you can have the PMBOK (not the new PMBOK), then you can select the life cycle and after that you have to put available the list of things that can be taken to fill it up. A good example of a framework is what you will find inside the Scrum Guide.
I'd suggest starting by developing a charter for this important project. That will help to establish the boundaries for the work but also ensure that there is alignment across all senior stakeholders.
If your company doesn't presently have any PM standards, my recommendation is always to start by identifying delivery & control objectives and then develop a minimal, flexible set of standards which will support achievement of those.
When designing a solution, the first step is to clearly define the problem itself.
There are many existing frameworks that are better or worse suited for different types of projects. What works for major infrastructure with long lead times and where changes may be extremely expensive will be different than software where changes may be implemented in days or weeks with little collateral impact. What differentiates a good solution form a bad one in your own situation?
You don't have to reinvent the wheel, but you can customize an existing invention to your own needs. Examine different methodologies for what fits your business to familiarize yourself with various options and develop a starting point to build upon. That becomes your rough framework.
You can try a bottoms up approach by picking the minimum parts to fit your needs. That can be difficult and error prone with little experience. I prefer to start with existing standards and tailor them down to my own needs.
The PMBOK process groups is one starting point. My 1st electronics project I found the IEEE WBS template standard and tailored a long document down to a short list. Others before you spent a lot of time populating those standards to address every possible case they could imagine. Use their prior work, to pick the minimum set for your own needs.
...
1 reply by Chris Oroho
Nov 16, 2021 7:23 PM
Chris Oroho
...
Thanks Keith, very insightful.
Saving Changes...
Chris OrohoSenior Internal Auditor| National Fisheries AuthorityPort Moresby, Ncd, Papua New Guinea
Nov 16, 2021 5:09 AM
Replying to Sergio Luis Conte
...
Key thing is to understand what a framework is. Is like a MS Word template for example. You have the main structure and you have to fill it up with the techniques and methods that best fits for each initiative and the environment. For example, you can have the PMBOK (not the new PMBOK), then you can select the life cycle and after that you have to put available the list of things that can be taken to fill it up. A good example of a framework is what you will find inside the Scrum Guide.
Thanks Sergio..very helpful hint Saving Changes...
Chris OrohoSenior Internal Auditor| National Fisheries AuthorityPort Moresby, Ncd, Papua New Guinea
Nov 16, 2021 8:00 AM
Replying to Abolfazl Yousefi Darestani
...
I do agree with Kiron.
Thanks. Well noted. Saving Changes...
Chris OrohoSenior Internal Auditor| National Fisheries AuthorityPort Moresby, Ncd, Papua New Guinea
Nov 16, 2021 11:40 AM
Replying to Keith Novak
...
When designing a solution, the first step is to clearly define the problem itself.
There are many existing frameworks that are better or worse suited for different types of projects. What works for major infrastructure with long lead times and where changes may be extremely expensive will be different than software where changes may be implemented in days or weeks with little collateral impact. What differentiates a good solution form a bad one in your own situation?
You don't have to reinvent the wheel, but you can customize an existing invention to your own needs. Examine different methodologies for what fits your business to familiarize yourself with various options and develop a starting point to build upon. That becomes your rough framework.
You can try a bottoms up approach by picking the minimum parts to fit your needs. That can be difficult and error prone with little experience. I prefer to start with existing standards and tailor them down to my own needs.
The PMBOK process groups is one starting point. My 1st electronics project I found the IEEE WBS template standard and tailored a long document down to a short list. Others before you spent a lot of time populating those standards to address every possible case they could imagine. Use their prior work, to pick the minimum set for your own needs.
Thanks Keith, very insightful. Saving Changes...
Chris OrohoSenior Internal Auditor| National Fisheries AuthorityPort Moresby, Ncd, Papua New Guinea
Nov 16, 2021 7:36 AM
Replying to Kiron Bondale
...
Chris -
I'd suggest starting by developing a charter for this important project. That will help to establish the boundaries for the work but also ensure that there is alignment across all senior stakeholders.
If your company doesn't presently have any PM standards, my recommendation is always to start by identifying delivery & control objectives and then develop a minimal, flexible set of standards which will support achievement of those.
Kiron
Thanks very helpful. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Chris, Developing a PM framework or a methodolgy for an organization is what most PMOs do. They standardize life cycles, processes and more to enable comparisons and transparency, continuous improvement as well as transferring people between projects.
PMBoK ed6 as process driven standard was used by many as a template for their own framework or methodology.
Not sure if ed7 is similarly suitable for this purpose.
"This planet has - or rather had - a problem, which was this: most of the people living on it were unhappy for pretty much of the time. Many solutions were suggested for this problem, but most of these were largely concerned with the movements of small green pieces of paper, which is odd because on the whole it wasn't the small green pieces of paper that were unhappy."