Methodology
The Way We Work
-
Oracle
ManSoft adopts a flexible implementation methodology within the project life cycle. This is built around Oracle's AIM (Application Implementation Methodology) and based on ManSoft's extensive experience in the implementation and integration of large complex information technology projects.
The AIM methodology is a framework of related elements. It involves phases, processes, tasks and dependencies:
- A task is a unit of work, which results in a single deliverable. That deliverable may take many different forms like reports, schedules, code, or test results for example.
- A process is a closely related group of dependent tasks, which meets a major objective. A process is usually based on a common discipline.
- A phase is a chronological grouping of tasks. It enables a flexible way to organize tasks, schedule major deliverables, and deliver projects.
The following diagram provides an overview of AIM, highlighting the processes and phases:
-
Microsoft
General Project management approach:
Our project management approach ensures that the project is completed:
- On Time
- Within Budget
- According to specifications &
- Following high quality standards
Initial Project Kick off:
ManSoft in association with its Clients spells out the project scope addressing key business areas. ManSoft and the client will establish Project Organization in terms of Steering Committee and Project Committee and will outline Roles & Responsibilities of Project teams from Client and ManSoft. ManSoft would analyze dependencies for each activity of the project and jointly workout a detailed plan.
Resources:
Identification of Project Managers and Process Owners:
On finalization of the order, the client shall appoint a Project Coordinator and / or the Process Owner. ManSoft will form a project team with a Project Manager / Project Leader and team members.
Project Team Structure:
The project reporting structure would typically be as follows:
Monitoring and Control Mechanisms:
Kick-off meeting:
The project will be formally initiated by a Project kick-off meeting. The client's Project Coordinator, (and/or the Process Owner) will attend this meeting and other members of both organizations as may be deemed necessary.
SRS and scope of work:
The broad scope of work and boundaries are detailed in the System Requirement Study (SRS) that shall form the first stage of the project. The SRS will be discussed with the Project Coordinator / Process Owner and the same will be signed off as constituting the agreed scope of the project.
Change Management and Review/Sign-off Procedure:
Any change in functionality with respect to the base functionality signed-off in the SRS is handled through a Change Management process conforming to our Quality Management Process. Essentially, this involves the client filing in a formal change request to the Project Manager / Project Leader, who will then make an impact analysis of the change on the time and cost.
Review Meetings:
Weekly/fortnightly review meetings are conducted to review functionality issues and progress of work. The frequency of meetings is mutually decided during the project kick-off meeting. All matters that are not resolved during the review meeting are escalated as per the escalation procedure.
Progress Reporting and escalation procedures:
A weekly/fortnightly progress report is prepared and submitted to the Project Coordinator (and Process Owner) and the Delivery Head of ManSoft. These reports indicate the progress of work and matters that need escalation or which are pending for decision.
Acceptance Testing:
A firm strategy is created and executed for creation of the test cases. Test cases are based on the Business Requirement Specifications documentation to verify the system performance. Test cases are divided into functional and technical tests.
Training:
Training is an important part of the entire roll-out. This phase involves training the client personnel in using the system both from a technical and functional perspective. ManSoft proposes to adopt a 'Train-the-Trainer' approach whereby a core team of the client is well trained on the intricacies of the application.
Documentation:
We provide following documents at the time of final delivery:
- User Manual
- System Configuration [Installation] Manual
- System Administration Manual
EMS
