10.1 Procedure no: 0.0
10.2 Procedure Title: Procedure for executing CDID:pm4g compliant projects
10.3 Objective: To define the process for the creation, execution and archiving of HRI projects using basic (i.e. free) Google tools in sufficient detail that further formal procedures are not required - although some tutorial or training materials probably will be.
10.4 Summary
This is a QA901 format procedure for managing a business or engineering project through its life cycle using the basic (free) Google products to host and collaborate the project documentation and collaboration process. This assumes that the project team is geographically dispersed, has limited ability and funds to travel and meet on a daily basis - but does have high bandwidth Internet access and is relatively computer literate - or is willing to become so.
This procedure applies specifically to all project being carried out at Hammond River Institute using the Infosys2 Knowledge Management system (currently a work in progress under project hri07e), but is offered as guidance for anyone looking for a low cost, secure, web based infrastructure for doing virtually all of the work required by most business and engineering projects for Small and Medium Enterprises.
10.5 Workflow
This may be a flowchart with branching and loops and may even be automated.
10.5 Procedure Steps
Human readable narrative descsriptions of how to do the work - complete with safety cautions.
10.6 Procedure Source Code
For automated procedures
10.7 Key Codes produced
The following Key Codes are necessary (but not sufficient) for all pm4g projects:
pm:wo - a work order (project) number:
pm:wotitle* - a work order (project) title:
- a Project Owner
-
* = indicates that a future key code to be defined when the Special Interest Group identified gets around to it.
10.8 Data Output files
These are one or more CDID's - but usually are the Primary CDID for the procedure.