Project Name - Allstate Insurance, DPS Support PID - 93939 Sr. No.

1 Audit Questions Project Overview Total Team size (Ratio of Technical:Domain:Testers:Managerial) Number of BAs (if no designated BAs / BSAs, then count of resources responsible for business / systems analysis work) Names of BAs / BSAs on the project and their location (if no BAs / BSAs, then name of person responsible for business / systems analysis work) Type of project Project Duration Pricing - Fixed or T&M

Scope of the project? Provide high level details of the business and technical aspects of the project

Project objectives and goals as set by client. Specifiy clearly with details.

Roles and responsibilities of BAs on the project (for each BA and collectively for the business analysis function). As much details as available will be most welcome. For example - If the role is Gap Analysis, then provide details of gaps between what, why and how they are doing it. LOB of project. Kindly provide details of types of products in this LOB, product highlights and the process involved Areas the BAs work in. For e.g PAS, Claims, Rating etc Ratio of Onsite and Offshore BAs

Extract of the SOW which has details regarding how requirements management, business analysis etc will be done

List of all upstream and downstream systems involved if any in this Project. For e.g if the PAS interfaces with the Billing system then details of the Billing system to be provided 2 BA Skills required in the project Level of experience of each BA required in the Project Ratio of domain and technical knowledge required. Please elaborate and provide reasons for the ratio. Technical skills expected from BAs in the project. For e.g ability to read code and extract business rules What is the JD of the BA / BSA role given by the client? Especially for Staff Augmentation requirements 3 BA practices followed by the team What kind of collaboration takes place between BAs from client and vendor and between BAs onsite and offshore. Please provide details Who is primarily responsible for gathering and documenting requirements? Client or Syntel? If the requirements are provided by the client, then is there a dependency on client BAs and are they effectively been able to communicate the business needs? Please elaborate If the onus to gather and manage requirements rests with Syntel then do our BAs interact directly with the Business SMEs/User or do they have to depend on the IT teams? Please provide details How are requirements captured or obtained? Are there regular interactions with client, SMEs or Business Users (Example - for review, updates etc). IF yes, what type of interactions and periodicity of these interactions What are the documents received from the client wrt business/functional requirements? List down the names and description of documents Types of documents created by the BA. List down the names and description of documents Do you document any Process Manuals / System Manuals / Process Flows? If yes, provide details - What, How, When, Name & Description Is requirement traceability done? If yes, please provide details. For example - Traced from requirements to test cases Is there any extraction of Business Rules required in this project? If Yes, then please explain If yes, how are business rules recorded and maintained?

Are there any specific tools used by BAs in the project? For e.g Req Pro What type of KT was done with the client at the time of Project initiation and during the course of the project? Please provide details Is there a requirements walkthrough made by the BA to the client BA or Business Users during the course of the project? Are we using the client's or Syntel's templates? If the answer to the above is Client, please share the list of templates Is there a requirement sign-off process in place agreed by both the parties? If yes, are there any challenges in achieiving this? Is there an escalation procedure for resolving delays on sign offs? If yes, provide details Is there a process for Change Request and is it documented and followed? Explain what is the CR process for the project? What is the escalation procedure in case CR procedure laid down is not followed Is there a Disaster Management system in place for back ups especially those in Shared Folders/VSS Has there been an occasion to escalate any requirement or sign off issue to the Governance Council? Who is responsible for initiating the escalation procedure? What is the role of the Lead BA in this regard? Is there any type of prototyping done for this project? If yes, how is it created?

Explain your learnings in terms of BA work performed.

BA/BSA Trainings required & imparted What type of feedback was received on our BA / BSAs from the client - formal or informal? Please provide highlights of the feedback What are the problems faced by BAs in meeting the requirements of project? What could be the probable reasons for the problems? How was this challenge addressed? Please provide details Are there any continuous trainings provided to the team members for upgrading skills required for the project? Please explain Any unique skills / expertise required by BAs for this project? E. g. ACORD data mapping, product knowledge, regulatory requirement etc

Other details

Have we lost any BA / BSA opportunity at onsite or offshore due to non - availability of such skills or travel readiness? If Yes, then reason for loss of the opportunity Have they been undue delays of any kind during the course of the project? Please provide details What is your opinion on the quality of the knowledge shared by the client for this project? Any other vendor working on this project for the client? If yes, in what area and scope of work? 6 Any other BA related information that you wish to provide

Response Project Overview 20[5 onsite+15 offshore] 14:1:3:2 1 BSA Prashant Goswami 1 BSA. Location Northbrook Maintenance till 2014 Fixed Capacity Production support service[Non Discretionary service] Maintenance service Project Management service Business Analysis service QC services Provide customer with high levels of availability reliability and transaction response time with SLA to be defined within scope *Reduce defects and TAT for reported problems *Reduce and control the operating costs *Leverage experience in NG DPS application syste mto facilitate better service Requirement gathering and Analysis. Major focus during Pursuit phase and Analysis & Design phase. Communicate with all the teams involved in a work request, understand the deliverables for each phase, communicate with the internal team and make sure those deliverables are delivered on time. Claims Property and Casualty (includes first party claims, third party claims, auto and subrogation) Claims Ratio is 1:0 *Conduct Meetings and gather requirements *Discuss with Business SMEs and create Mockups *Update Requirement database with Template details such as Keywords etc., *Provide business knowledge to verify defects and incidents *Co-ordinate business requirement implementation with the development team *support development team to resolve any business queries Support user acceptance & QA testing and validate the test results.

Response required from PM PM PM PM PM PM

DM/EM

DM/EM

PM/DM/BA

BA PM/BA PM

DM/EM

NextGen FNOL system NextGen Claims system OPC - Output Processing Center BA Skills required in the project Intermediate level of BA would suffice 2:1. More domain knowledge is needed than technical knowledge. Would need Technical knowledge in EDINAT tool to understand and create mockup. Technical knowledge in EDINAT tool NA BA practices followed by the team The client BA gets the business requirement and Syntel BA does a feasibility study and gives input on the technical solution related to the project along with the plan (resource and timelines) Client Yes

DM/EM

PM/DM BA/PM BA/PM PM/DM

BA/PM BA/PM BA/PM

Yes For a work request, its through requirement documents and for templates its through mockups (a word document describing business rules) Yes. For template changes, its almost everyday during pursuit and A&D and it reduces as the phases progress. Initial Requirement document- beginning of pursuit phase Final Requirement document- end of pursuit phase Conceptual design document- end of pursuit phase Initial and Revised Estimates- beginnnig of pursuit phase, end of pursuit phase and end of A&D phase No No We have regular template work as well in which the business rules are spelled in the word document, we have to interpret these logic into the proprietory tool that we use The business rules are recorded and maintained in the mockups (word documents) of each template

BA

BA

BA

BA/PM

BA

BA/PM BA

BA

No 1. Explaining the system flow 2. Explaining the sharepoint document structure and process that needs ot be followed to raise a change request 1. Explaining the system flow 2. Explaining the sharepoint document structure and process that needs ot be followed to raise a change request Client Estimation Template, Design document template and Test plan template Yes No Yes. CR Document will be created and slotted into a NextGen release None No. Documents in WSS. Back up available in NAS. No BA/PM is responsible to escalate No 1. Gaining business knowledge wth respect to claims, since there is a dircet interaction with the business 2. Understanding and implementing the release plan 3. Project planning and capacity planning BA/BSA Trainings required & imparted Informal. No major concerns. Scope management. Business expectations are different than IT release planning. Got exception to execute monthly release NA NA Other details

BA BA

BA BA BA/PM PM PM PM PM PM PM PM BA/PM

BA

DM/EM PM/DM/BA PM/DM/BA PM/DM PM/DM BA

No No Sufficient No No

DM/EM DM/EM DM/EM PM / BA PM PM / BA