Project Implementation

Project Initiation: In this stage Business analyst, Delivery head and Prescale-consultant will meet client and they used to prepare Scope document. This document contents requirement with brief information (Most info) about Application.

Example: How many approval level they need, what is hierarchy structure, Invoices and payment…etc.

Based on scope document business analyst and delivery head will start recruitment of team. They make decision about man power, working hour and Project delivery time. Once scope document is freeze (Accepted by both sides) then we will move to next step.

For that they will send few team members to their place to get more information.

Onsite documentation:

RD-20 Document: In this document we used to prepare Standard questioners for Each and every module (GL, AP, AR, and FA & CM).

In this document we used to gather in-depth information about client requirement 

BP-40 Document: In this we used to gather Current business model information about legacy and processing methods, this document is called as a “As-Is doc”.

Example: Invoice, Payment, Purchase orders, sales and ledger books…..etc

BP-80 Document: In this we used to prepare future business model information based on RD-20, BP-40 and Scope document, this document is called as a “To-Be doc”.

Example: Invoice process, Payment method, Purchase orders, sales and ledger books…..etc

MD-50 Document: If there is any difference b/w BP-40 and BP-80 they fixed it in document this document is called as a MD-50 document (Module design) based on this they will conduct Gap analysis and if any customization Done will prepare MD-50. Based on MD-50 technical people will prepare MD_70.

Three types:

1. Work around
2. DFF
3. Customization

Offshore Documentation:

BR-100 Document: (Business process requirement documents) it is nothing but setup documents in this we will prepare all setups for each module and prepare this doc by using screen shots and navigations.

TE-40 Document: will prepare test script for testing purpose. First we will go through the RD-20, BP-40, BP-80 and scope document we will prepare test scenarios, based on scenarios we prepare test scripts.

Prepare doc for Data input, Expected Result and Status Result.

Testing we will do manual testing there are few type in manual testing:

1.      Unit testing

2.      Process testing

3.      System Integration testing

v  Code reviews

v  Bug reviews

Once it is bug proof we go for next step…..

CRP instance:

CRP1 (Conference room pilot): we will explain with screenshots and key points. In this stage Process experts, Application implemented team and Project heads from both side will sit together explain process, Still if they have any modifications we note all points raised by Process experts.

In this Client is ask for additional requirement or modification is the process, we will consider it as a “Change request (CR)”.

CRP2 (Conference room pilot): Once modification done based on CRP1 we will explain with screenshots and key points. Still if they have any modifications we note all points raised by Process experts.

In this Client is ask for additional requirement or modification is the process, we will consider it as a “Change request (CR)”.

Like this we make this process till Squire off Change request raised by Clients and also we will do Regration testing.

Key User Training: In this stage we have to prepare User manuals, Power point presentations to provide training and assistance to Process experts about application process methods.

User Acceptance Test (UAT): In this stage Process experts (End user) will test application Access, Process methods, Reports and how much time it taking to generate reports.

Once UAT is done accepted by Process experts then they will go for “UAT Sign off”

  

Production Support: In this stage configure all setup in each module and Production begins immediately with the production cut over. It marks the last phase of implementation, and the beginning of the system support cycle. In this final phase is series of refinements and performance measurement steps.

v  MIS/IT Department personnel work quickly to stabilize the system and began regular maintains.

v  Provide the ongoing support to the organization for some time as SLA(Service level Agreement)

v  Compare actual result to Project objects.

In there is any issue from Client side for additional requirement or modification we will consider it as a “Change request (CR)”.