|
|
 |
 |
Methodology:
Proper project management practices will be required in order to ensure delivery of the project on time and budget. The roles of people involved with the project are explained here. It is possible, given the number of people involved, that in some cases the same person may perform multiple roles.
Project Steering Committee:
It is recommended that a project steering committee be formed (or its function attached to an existing committee) to overview the project and enforce the projects terms of reference. Its function should be:
 |
Provide senior management support for the project team |
|
Resolve policy, procedure, resource and political issues |
Any significant changes to scope, or budget would be required to be referred to this committee. The committee should not however get involved in day-to-day issues. The committee should meet regularly; say fortnightly, to review progress of the project.
Project Sponsor:
A member of senior management who is committed to the project and has the authority to intervene if required resolving any issues quickly. When the system is going live their role is to use their authority to ensure compliance if there is no cooperation amongst the users.
Client Project Manager:
This person will have the responsibility of the day to day running of the project including:
|
Oversee all day-to-day aspects of the project |
|
Main point of liaison with Provida during
the project |
|
Co-ordination of Client resources |
|
Communicate progress of client project deliverables to key Client stakeholders |
|
Provide expertise and guidance in either the business or data processing area of the project |
Provida Project Manager:
This person is responsible for the timely delivery of the Provida deliverables and implementation of the system in such a way to achieve the best use of
Sage Accpac ERP or Microsoft Dynamics by the Client. Their role includes:
|
Co-ordinate provision of appropriate Provida resources |
|
Keep Client management informed regarding progress of deliverables, budget and schedule |
|
Bring any issues regarding the project to the attention of Client management in a timely manner |
|
Work closely with the Client Project Manager and team |
Provida Senior Consultant:
Provida will allocate a Senior Consultant who will lead the consulting services provided to the client. This means that this person will perform most the consulting work required in installing, configuring the system and compiling any issues list.
The Senior Consultant will report all progress back to the Project Manager.
Provida Software Engineer:
The Software Engineer will perform all customisation and programming services and also some or all of the Crystal Reports Development. Any specification used by the Software Engineer will generally be prepared in conjunction with the Senior Consultant. The Software Engineer may also be called in to setup the database software, resolve technical issues related to the operating environment.
Provida Systems Consultant:
It
is the standard practice of Provida to introduce
a second consultant to the client’s site to ensure that more than one Provida staff member has an understanding of the client’s business. This person may be also a Senior Consultant.
System Owner:
The system owner is the person who is responsible for the system internally. This person will be the main point of ongoing contact for Provida after the completion of the project. They will be responsible for:
|
Managing any ongoing support issues |
|
Ensuring that the Client continues to get the most from the system |
|
System maintenance and upgrades |
|
System security |
|
Principle contact |
Provida Account Manager:
The Account Manager is responsible for managing the sales process. The Account Manager will become involved from Agreement on Need. The Account Manager will attend the initial handover meeting with the Senior Consultant and or Project Manager. After the initial handover meeting, the Account Manager will only be involved if additional software is required.
Progress Reporting:
Project Managers may meet periodically to review progress and outstanding issues. This meeting may take face-to-face or by phone depending on the nature of the meeting. This meeting should:
| 1. |
Managing any ongoing support issues |
| 2. |
Ensuring that the Client continues to get the most from the system |
| 3. |
System maintenance and upgrades |
| 4. |
System security |
| 5. |
Principle contact |
Microsoft Project will be used to create a project plan and gannt chart. Milestones will be recorded as a part of this planning process.
Progress against the project plan may optionally be reported either on the Client intranet or the Provida's website. This will allow management and other stakeholders’ access to information about the project status .
Scope Changes:
Guarding
against scope change is critical to delivery of the project
on time and within budget. However if change is required then a Change Order needs to be completed in writing and approved by either the Client Project Manager and/or the Steering Committee.
Budget:
The project as outlined in the project plan is being completed by Provida on a time and materials basis. Charges for out of scope work or action by the Client that results in additional time being incurred by Provida will be billed. Matters of this type will need to be agreed by both Project Managers.
Project Room:
On-site facilities including ready access to a network, printer, and direct phone line for modem access, white board, a desk, ergonomic chair and telephone would be desirable for a period around the live date.
Click here to visit our Internet Partners |
|
 |
 
 |
