Erik MillerStrategic Project Coordinator| CMEAmericaLakewood, Co, United States
Hello all,
I am new to project management and I work for a company without PM experience. I have been tasked with creating a project management process/SOP for the company and while I have the writen portion almost complete I am stuck on what elements to include as must haves for every project e.g. project charter, risk assesment etc... Can anyone help me identify what the most basic of projects should/must include please? Saving Changes...
Jaleel .PMP, Associate Director| MetricStreamBangalore, India
I also agree. PMBOK is the one to look for details. Saving Changes...
Nilima DeshmukhProject Controller| Schneider ElectricNashik, Maharashtra, India
Hi,
As all the friends of ours said you should go to PMBOK guide and most importantly concentrate on the process charts to better understand which various inputs, outputs and tools and techniques will be applicable to your type of project.Also try to correlate various inputs/outputs. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Good comments thus far. And you can see the common theme. Don't create process for the sake of process and don't create documentation for the same. Ensure there is a need. Start there. Documentation can be aligned with the size/type/complexity of the project, with a fundamental requirement spanning all.For instance, all should have some semblance of a charter - what is the need, intent, goals, general scope, etc. Saving Changes...
It depends on your specific project for what specific artifacts/deliverable documents will be needed. The PMBOK provides good guideline. There are many example documentation here on the site which you could use as well. Saving Changes...
Many PMs make the mistake of thinking that project management is formulaic - if they create such and such documentation and implement so and so processes, their project will be an automatic success. This is untrue.
It is crucial that you understand *why* you're creating a piece of documentation or performing a process. To achieve this you must know such things as the business reasons driving the project, the project's business and techincal requirements, and different risks that might affect it, etc. When you can answer those questions, it will be evident what process you need to implement and - most important of all - how to implement them.
Yes I tend to agree more with this. Best option for you to start is for you is to look at the project repository / database in your company and identify the artifacts (SOP,project charter, risk assessment etc) of similar projects completed. You can take those artifacts/templates and start your work from there. Also talk to fellow project managers who have completed similar projects and refine your work. Hope that this helps. Saving Changes...
Elizeu AntonioManager for Network Operations| MSTelcomLuanda, Angola
I agree with Kiron and also with Andrew. A defining point for professional work is valuable skill. Thus, you will have more credibility to propose and implement improvements on the organization and make project management process/SOP to serve a valuable purpose. Saving Changes...
