Hello all,
My organization does not have a structured approach to PM and I have been tasked to implement a framework for different types of projects we may encounter (capex, NPI/NPD, supply chain, contractual etc)
I want to start with a basic framework that everyone can start following. I am afraid about discouraging people if I make it very complicated right at the beginning of such an implementation.
Are there any suggestions anyone of you can provide, if you have had similar experiences? More than the starting point, I am confused about where I can end this framework - atleast the first phase of it.
Best regards
Balaji. Saving Changes...
Sort By:
Marek RudnickiPMO, Program Management, Project Management, Business Development| FreelancerPoland
Hi Balaji,
Obviously not knowing all details of your request I can see two aspects.
When saying PM Framework:
1) Are You looking for a Project Management methodology, e.g how to run and manage projects?
If so, do you have professional PMs on the team?
I would assume they know how to manage projects from their experience. You may want to have one standard on this, but from a practical perspective when I have professional PMs on the team I let them do projects according to their best practice gained from past experience and certificates.
Of course, It may be not the case for You.
2) Are You looking for basic governance of projects in your organization - e.g. PMO standard?
I would assume your request is more on this. (I may be wrong of course).
In this case, You may want to define the basics and get this agreed upon in the organization:
- roles like PM, Sponsor, PMO
- how to initiate the project
- when and what to whom to report status in your organization
- how to manage financially, risk, etc - key elements organization
- what to have control
- how to close the project.
I think these are the basics.
...
1 reply by Balaji Varadharajan
May 16, 2021 11:48 AM
Balaji Varadharajan
...
Marek,
Thanks for your reply. I am looking for both points 1 and 2 that you have listed, leaning more towards point 2.
I want to create a PM standard, and also define the stages that a project has to go through depending on what kind of a project it is.
Thanks
Balaji.
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Balaji,
you are right, not making it complicated in the beginning (or later) but simple to grasp and beneficial to the project managers and the sponsors is important.
Why not gather some requirements and pains from the key stakeholders, prioritise them (with the sponsor), and communicate what you will do with them. You could simply start by having regular open meetings and get your requests from them as well as starting to build a PM community sharing good practices.
I saw that people long for standardisation if they are living in chaos. They can often deal with their own work but struggle to get the interfaces right.
What you are doing is establishing a PMO and it is a project. Once the PMO is up and running, it needs continuous improvement and development but also steady state operations. There are many tips out there how to start a PMO. Get some advice, a mentor or even hire a consultant for the first months.
Thomas (running PMOs since 1995) Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
What you are putting focus is on the life cycle you will choose. With base on the life cycle you can add what some organizations promote as best practices to perform project management. For example, if you ask me, in your case, I will go to PRINCE2 because it has a life cycle and it is aligned with best practices like stated into PMBOK. All these taken into account you are creating solution where solution is equal to the thing to be create plus the way to create it. The way to create it must be defined after making an enterprise analysis. For example, the new wave is taking agile approach but few people try to understand what agile means and after that to evaluate if the enterprise architecture is ready for using it. If you do not that then you are adding a problem to the solution component then you will not create the solution. With that said, to do this type of things is one of my duties for long time ago. In my actual work place we have defined 5 different ways to create solutions and we defined the selection criteria which is driven by the type of solution to create, as you stated above. So, if you need to go for something rapid to use, go for PRINCE2, understand it, use it and adjust according to the feedback you are receiving from all layers inside the enterprise architecture. Saving Changes...
Obviously not knowing all details of your request I can see two aspects.
When saying PM Framework:
1) Are You looking for a Project Management methodology, e.g how to run and manage projects?
If so, do you have professional PMs on the team?
I would assume they know how to manage projects from their experience. You may want to have one standard on this, but from a practical perspective when I have professional PMs on the team I let them do projects according to their best practice gained from past experience and certificates.
Of course, It may be not the case for You.
2) Are You looking for basic governance of projects in your organization - e.g. PMO standard?
I would assume your request is more on this. (I may be wrong of course).
In this case, You may want to define the basics and get this agreed upon in the organization:
- roles like PM, Sponsor, PMO
- how to initiate the project
- when and what to whom to report status in your organization
- how to manage financially, risk, etc - key elements organization
- what to have control
- how to close the project.
I think these are the basics.
Marek,
Thanks for your reply. I am looking for both points 1 and 2 that you have listed, leaning more towards point 2.
I want to create a PM standard, and also define the stages that a project has to go through depending on what kind of a project it is.
Thanks
Balaji. Saving Changes...
Peter RapinSubject Matter Expect; Project Delivery| Independent ConsultantOntario, Canada
The key is why are you being "...tasked to implement a framework for different types of projects?" Is there a problem requiring a solution? What needs to be improved? Is there a communications issue? a performance issue? lack of documentation? You have been provided the solution - "implement a framework" but it seems the problems needs definition. Note, many projects are delivered without "a structured approach".
Once you define the most pressing problem implement project management procedures to address that problem. Once that is done, go on to the next problem. Ultimately you will have a structured PM approach - not only that but you will have solved immediate problems on the way. By showing that a PM structure solves problems you will get much needed support and less negative reaction to your initiatives.
