You might consider handling this like writing a procedure.
1: Define the purpose of you project management process.
2: Define the scope of the process. Will it encompass continuous improvement? Preventive action? Product/process corrective action? Internal audit corrective action.
3: Define the responsibilities for project management. Who will coordinate project? Who will approve projects? Who defines the project budget? Who verifies project effectiveness? Who approves closure of the project. Who reports project resilts?
4: Brainstorm the ideas and begin putting together a flow chart.
5: Define what instructions are required and what documents need to ne in place to record effectiveness (or lack of effectiveness).
6: Train, Train, Train.
I have either a procedure or flow chart (not sure, been a long week) I could send you if you email me.
ASD...
------------------
Al Dyer
Mngt. Rep.
ullysses3@excite.com
I use MS Project because everyone has it and it does what I want. You do as Al said - outline your steps. Prediction is a lot of project management as is the 'gift' of being able to coordinate and communicate with folks (personality).
Many companies use spreadsheets for tracking a project. The software you use really depends upon the 'power' you need (such as resource tracking, costing, etc.).
How should I start with the details for project management?
Linear Mode
