Each Project follows the same project phasing:

• Assess phases (Analysis,
• Design, Project Planning, Audit, Architecture, etc.);
• Build phases (Development, Configuration & Implementation, User Testing & Acceptance, Preparation for Deployment & deployment, etc.);
• Run phases (Post Go Live, Maintenance, Support, etc.).

A. ASSESS

This initial ramp-up phase aims at identifying all that is necessary for the initialization and the launch of future phases. This phase is intended to agree, understand and clarify a functional scope, a technical architecture, audit an existing solution, and to define the next Phase.

• Data Gathering: workshops and interviews with the Client to understand Client’s exact needs, requirements, issues, and collect all processes, documents and other information which will be necessary or useful to the Project. A number of functional and technical workshops may take place at this stage.
• Wrap-up: a single meeting to review all data collected, to confirm:

             -  All data is accurate and helpful;
             -  There was no misunderstanding in the exchange of information, and review corrections if necessary;
             -  Confirm that the data gathered is complete, and that no element, not communicated during Data Gathering will be introduced at a later stage.

 

B. DESIGN

• Analysis and design proposal: all the data gathered is analysed, classified, possible solutions are evaluated, recommendations are made as the case may be, in order to deliver:

                 -  The functional scope of the following phases;

                 -  The task list of each following phases;

                 -  The deliverables for each phase;

                 -  The planning of the phases;

                 -  The phases cost;

                 -  The staffing.

• Kick Off: formal agreement with the Client as to the functional scope (in and out), Project methodology, deliverables, Project cost and Project planning. 

C. BUILD

During the Build phase(s), SiM’s team will create and provide the following deliverables:

• Source codes;
• Configuration;
• Documentation, as the case may be;
• Internal Tests plan and tests (results);
• Bug correction;
• Installation and Deployment guides;
• Other agreed upon Deliverables;

SiM has the obligation to produce and deliver the above according to the agreed upon specifications & planning, which must meet the client’s expectations.

 

D. RUN

•  Maintenance 

During the regular use of the application, users may encounter issues. All such instances must be reported, as quickly as possible as a Ticket. A Ticket is an atomic piece of information which must cover a well defined perimeter. Tickets which are opened for several different issues must be broken down in different tickets.

•  Requests for change 

If during the Project, a functionality, feature, module or other element is requested by the Client but is however not included in the agreed upon Scope of the Project, the Client shall be informed of the Out of Scope nature of its request. The Scope of the Project is bound by contract and the details specified during the Assessment Phase.

Client’s request shall then constitute a Request for Change.