Project Management

Please login or join to subscribe to this thread

Project Management Documents

linkedin twitter facebook   Governance   Information Technology   Lessons Learned   Work Breakdown Structures (WBS)  
avatar
Lara Doll Project Manager, CAPM Fort Worth, Tx, United States
Hello everyone,

In regards to major documents for a project, I've seen many different opinions on this and I would like to see what people in the trenches actually use - when they are developed and how they are put into play.

For example, I see some people mentioning a Business Case, and then others don't mention this, but are keen on a Project Charter.

What are the major documents you use? When are they created and put to use?

Thanks for your replies in advance! :)
Sort By:
< 1 2 >
avatar
Lara Doll Project Manager, CAPM Fort Worth, Tx, United States
Nov 15, 2018 11:24 PM
Replying to Drew Craig
...
And now with your new found knowledge, you can begin to set the guidelines for your organization, and champion a formal process going forward. Great opportunity!
Very true, Andrew. Thanks for pointing that out! You'd think I would have thought of that by now, but 'doh!' I'm the guinea pig AND the trailblazer!
avatar
Vivek Pandey Process Manager| Ericsson Global India Pvt. Ltd. Fatehpur, Uttar Pradesh, India
Is there any standard template or documents do we need to use, when handing over project to operation team? If yes, please suggest some standard documents and template.
...
2 replies by Dinah Young and Keith Novak
Feb 25, 2019 9:04 AM
Dinah Young
...
In our Project Completion Document - https://www.projectmanagement.com/delivera...mpletion-Report there is a section for handover. We list any steps required for handover, any follow-on actions needed and any additional information.
We have a Customer Service group as well. I have created documents for reviewing a new application with them so that they know how to handle any calls. This includes documenting some the suspected issues users may have, like access, etc.
Feb 25, 2019 12:34 PM
Keith Novak
...
Individual organizations may have standardized documents for this, but it will necessarily vary quite a lot depending on the type of project. For example, the operations team implementing a new business management system in health care will have significantly different needs than for a large scale infrastructure process like a water treatment plant.
avatar
Dinah Young Project Manager / Software Asset Manager| Prince William County Springfield, Va, United States
Feb 25, 2019 1:34 AM
Replying to Vivek Pandey
...
Is there any standard template or documents do we need to use, when handing over project to operation team? If yes, please suggest some standard documents and template.
In our Project Completion Document - https://www.projectmanagement.com/delivera...mpletion-Report there is a section for handover. We list any steps required for handover, any follow-on actions needed and any additional information.
We have a Customer Service group as well. I have created documents for reviewing a new application with them so that they know how to handle any calls. This includes documenting some the suspected issues users may have, like access, etc.
avatar
Steve Ratkaj Ontario, Canada
Being the government, there are way too many project documents (plans) that we require, and we are trying to simplify what PM's need to produce and focus on those that bring value added. Producing a plan that sits on a shelf without ever being read is far too common. Here is a partial listing:

1. Project Brief
2. Project Charter
3. Project Management Plan (one for each project phase - 5 in total)
4. Statement of Requirements (SOW)
5. Business Case Analysis (BCA)
6. Sustained Business Case Analysis (SBCA)
7. Phase Report (one for each project phase - 5 in total)
8. Environmental Impact Assessment Report
8. Gender Based Analysis Plus (GBA+) Report
9. Deliver Expected Results (DER) Report
10. Integrated Master Schedule (IMS)
11. Integrated Master Plan (IMP)
12. WBS
13. Systems Engineering Management Plan
14. Configuration Management Plan
15. Quality Assurance Plan
16. Integrated Logistics Support Plan
17. Technical Data Management Plan
18. Training Development Plan
19. Risk Management Plan
20. Integrated Testing & Support Plan
21. Logistics Support Analysis Plan
22. Supply Support & PHST Plan
23. Technical Publication Plan
24. Test & Evaluation (T&E) Plan
25. Engineering and Support Management Plan (E&SMP)
26. Equipment Program Plans
27. Equipment Logistics Directives (ELDs)
28. Equipment Support Plan
29. Performance Management Plan
30. Risk Register
31. Change Log
32. Issue Log
33. Stakeholder Register
34. Lessons Learned Database
35. Project Diary
avatar
Keith Novak Tukwila, Wa, United States
Feb 25, 2019 1:34 AM
Replying to Vivek Pandey
...
Is there any standard template or documents do we need to use, when handing over project to operation team? If yes, please suggest some standard documents and template.
Individual organizations may have standardized documents for this, but it will necessarily vary quite a lot depending on the type of project. For example, the operations team implementing a new business management system in health care will have significantly different needs than for a large scale infrastructure process like a water treatment plant.
avatar
Sukhdeep Singh Director| Standard Insurance Oregon, Or, United States
This is a late response but it all depends on the project at hand and the organization you are part of.
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

The smallest feline is a masterpiece.

- Leonardo da Vinci

ADVERTISEMENT

Sponsors