Project Documentation
During initial launch of a project all members have the right to join as long as the appropriate documents have been executed. After formal project launch, members may still join a project if agreed to by founding project members (size of majority required is spelled out in the Project Statement).
Statement of Work (SOW)
Each project has an SOW, which sets out the scope of work of the project, provides background information and describes industry need for the project, defines the purpose of the project, identifies previous related work, describes advantages/benefits for participants, identifies potential participants, and anticipates time of completion. It also provides a detailed project plan, which outlines required resources, materials and processes, establishes a project schedule with milestones and addresses project monitoring. See an example of a Statement of Work.
Project Statement (PS)
This is the official document, signed by each participant‚ Äôs senior management, committing the organization to the agreed-upon resource and time contributions for each project that a member agrees to participate in. It also provides the mechanism for declaring background technology and specifies how this technology will be shared or not shared with other project members. In addition, the PS defines information sharing for the project, determining whether project information will be shared outside of the project team (and, if so, with whom) and defines a publication approval process. Finally, it provides a date for transfer of publication rights to INEMI, preferably less than 18 months. Review sample Project Statement.