| Project Management | ||
| Pro-Tess can call on a depth of expertise in order to undertake or support any or all of the following, whether it is a completely new design, a rebuild or enhancements to current operations. | ||
| 1. Requirements Capture: Discuss with the client the purpose behind the project; ensure tie-in to other projects & in particular the client's business plan. | 2. Project Proposal: Present to the client the initial proposal based on information gathered in the Requirements Capture phase. Get client buy-in. |  |
| 3. High Level Project Plan: Produce a document showing generic ideas & concepts. It should give a broad indication of time-scales but emphasise that a detailed study is required. | 4. Low Level Planning: At this stage, specific equipments can be proposed and a detailed costs estimate produced. A documentation framework, including all acceptance parameters should also be produced at this stage. | |
| 5. Sub-Project Definition: If the project is large, the chances are that there are some parts lying outside the critical path can be separated out and run on an individual basis. | 6. Resource Requirements Confirmation: Once the detailed plans are agreed, the resources can be assessed and initial Invitations To Tender documents (ITTs) prepared. | |
| 7. Time & Budget Review: Present to the client an updated estimate of the deliverables in terms of time & costs. Highlight any key points in the plan and, if possible, produce a Critical Path Diagram. | 8. Resource Allocation: The project is now fully underway. Staff are being deployed and equipment & accommodation acquired & prepared for use. | |
| 9. Project Realignment & Reviews: It is almost inevitable that a project will drift from it's initial planned course. Regular reviews give the chance to update the project and keep the client appraised of any changes. | 10. Operational Readiness Testing: Individual elements, processes & procedures are tested and agreed as fit-for-purpose. If the requirements have been accurately defined, there should be no problems at this stage!!!. | |
| 11. User Acceptance Test Definition: Should
be derived directly from the agreed client requirements and provide checks
that the whole system meets those requirements. No changes should be permitted at this stage. |
12. Documentation: A structure should have been defined in the client's requirements. This framework will have been populated during the project and contain all the client needs to know about what is being delivered. | |
| 13. Support & Training: Once again, this will have been covered in the client's requirements. Service Level Agreements (SLAs) will have been developed and support & training contracts signed. | 14. Sign-off: The client is happy with the whole project and signs a legally binding statement accepting the work from Pro-Tess. | |
| 15. Hand-over: The project team formally hand over the Project deliverables to the client's operational management team. All further changes are done under the client's existing configuration policy. | ||