1.0 Title: Project Infrastructure Agreement
2.0 Purpose: To get initial agreement on which tools and methods will be used for a given project. The number and type of project and information tools is evolving very rapidly and any given project may have a differences st of tools. However - all parties should understand ahead of time which tolls will be used.
This is similar to identifying the deliverables ahead of time by specifying the CDID's but may preceded that and be harder to change once in place.
for example: if all parties agree to use Google Docs in a certain way for a project - then changing that method after the project starts could cause a lot of grief and expense.
3.0 Usage:
4.0 Frequency
5.0 References
6.0 Responsibility
7.0 Ownership
8.0 Effort
9.0 Risks
10.0 Contents
- a list of apps
- a list of "methods" (i.e how the apps will be used)
- a list of access rights
<more>
11.0 MetaData
12.0 File Handling Policy
13.0 Procedures
14.0 Tutorials