ProfServProjects: Difference between revisions
From Open-Xchange
No edit summary |
|||
| Line 12: | Line 12: | ||
=Concept= | =Concept= | ||
==Resulting Documents== | ==Resulting Documents== | ||
If there is a template available for this type of document it is linked via its title.<br> | |||
*[http://demo.de Customer Implementation Concept] | *[http://demo.de Customer Implementation Concept] | ||
*several [http://demo.de SOW]s (preferrably one per topic) | *several [http://demo.de SOW]s (preferrably one per topic) | ||
=Implementation= | =Implementation= | ||
==Resulting Documents== | ==Resulting Documents== | ||
If there is a template available for this type of document it is linked via its title.<br> | |||
checked [http://demo.de Requirements Checklist] | checked [http://demo.de Requirements Checklist] | ||
=Approval= | =Approval= | ||
==Resulting Documents== | ==Resulting Documents== | ||
If there is a template available for this type of document it is linked via its title.<br> | |||
signed [http://demo.de Requirements Checklist] | signed [http://demo.de Requirements Checklist] | ||
Revision as of 09:24, 18 October 2011
This page aims to give a detailed overview of customer-projects accompanied by the Open-Xchange professional services team: The different phases and decisions as well as the documents necessary to accompany this process are listed here. The following diagram gives a birds-eye view of the whole process: [[[File:birdseye.png]]]
Initialisation
Resulting Documents
If there is a template available for this type of document it is linked via its title.
- Project Charter
- Formal Offer
- Basic SOW
Concept
Resulting Documents
If there is a template available for this type of document it is linked via its title.
- Customer Implementation Concept
- several SOWs (preferrably one per topic)
Implementation
Resulting Documents
If there is a template available for this type of document it is linked via its title.
checked Requirements Checklist
Approval
Resulting Documents
If there is a template available for this type of document it is linked via its title.
signed Requirements Checklist