Project Name - John Hancock - Unit Valuation PID - 93078 Sr. No.

1 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 Audit Questions Project Overview

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 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. 4 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 5 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? Any other BA related information that you wish to provide Other details

Response Project Overview 1:3:0:1 3 ( 1 onsite BSA, 1 offshore BSA and 1 Management Trainee) Theodore Isaac - Chennai, India; Viswanathan Sreenivasan - Toronto, Canada Others about 4 months T&M Current systems documentation for the Unit Valuation (UV) Front-End is obsolete and lacks sufficient details to meet the needs for future application development.

Response required from PM PM PM PM PM PM

DM/EM

Developers do not have enough application knowledge to understand the impact of changes being made. This affects UV Finance. When a change to the UV Front-End is required, they have to ensure that application knowledge is passed onto the developers. This increases development time, since resources have a higher ramp-up time. The objective of this project is to deliver documentation that will provide clear and concise detailed functional specifications. The documentation will be suited to meet the needs of both the developers and UV Finance. DM/EM

A Detailed Functional Specifications (DFS) document will be written for each functional group of the UV Front-End application. The specifications will: a. Contain table and column references. b. Contain reference information such as form names, report names, and process names c. Not contain techincal details such as SQL statements and code snippets. PM/DM/BA

BA

PM/BA 1:2 ( includes a Management Trainee at offshore) Offshore BSA: 1. Offshore BSA will reach out the Onsite BSA to elicit the requirements with a list of questions. 2. There will be regular calls during the morning hours scheduled between the Onsite and Offshore BSA for around an hour or 2 based on the number of questions from offshore to start with. 3. Time of the calls would be the time that would best suit both Onsite and offshore counterparts. Onsite BSA: 1. Onsite BSA will reach out to Application SME to elicit system questions and Business counterpart to elicit . PM

DM/EM

JH - Unit Valuation is a stand-alone system that has its own UV database. BA Skills required in the project

DM/EM

PM/DM Neither domain knowledge nor technical knowledge was required as this project scope was confined to just documenting an existing legacy system Moderate ability to read/understand the code BSA is required to understand the legacy system and translate the understading into Functinal Specification BA practices followed by the team 1. Book weekly 30 mins meeting with the Project Manager and Application SME(if needed) to a. Update the Project Status b. Highlight any Risks / issues / Challenges 2. Book 1.5 hour session with information resources and project leads to review DFSs (subject to the progress made and availability). 3. Book 30 mins meeting with BSA Practice Manager (JH and Syntel) to update on the progress (subject to preference and availability). Syntel No BA/PM BA/PM

PM/DM

BA/PM

BA/PM BA/PM

Yes

BA

Requirements are documented as system functionalities in the form of a DFS (Detailed Functional Specifications) Yes for getting pseudocode and reviewing DFS. Interaction was on need basis and done at onsite. UV System User Manual Vol 1 and Vol 2 Specification Management Plan (Onsite). Detailed Functional Specification (onsite and offshore) No No Yes, business rules were extracted from the existing system and code base Business rules were documented in DFS No Done at onsite Done at onsite Client

BA

BA

BA/PM BA BA/PM BA BA

BA BA BA BA BA/PM

Yes and no challenges associated No No No Yes No Onsite BSA and Lead BSA would interact with cliend and manage offshore BSAs No A good opportunity to enhance our documentation skills BA/BSA Trainings required & imparted

PM PM PM PM PM PM PM BA/PM BA

Client was happy with our work and our team has won an award from client's side. Eliciting requirements from offshore was a bit challenging initially. N.A As onsite co-ordinator was present at the clients side for eliciting requirements and help the offshore BSA None N.A Other details No

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

DM/EM DM/EM

No

DM/EM PM / BA

No NO

PM PM / BA

what type of project?

Which LOB Project caters?

Which area BA work in?

Is Prior experience required and if yes at what level ?

Description of document?

Please provide details

Please share the list of templates

Who maintained it?

IS there any specific reason?

Quality of knowledge shared by Client?

Identify BA opportunities in the project