Upgrade V2 to V3 - N.B.

At every stage you should be aware of what is billable a nd what is not in which case alwyas ask the Project Manager on your side. ---------- Preperation --------1 -> Feature and function matrix what we think you should have an possible confi guration options 2 -> Product Functional SPecification document 3 -> Once client decides high level Business requirements approved by their Busi ness then we create a custom function specification document 'Detailed Solution Overview'. This is highlevel solution for Client project team to understand what is possible in the new version of the product ---------- Requirements & Solutioning --------4 -> Next step both sit together and come up with details of the requirements in terms of exact requirements and impact on all systems and processes. This can b e included in the Detailed solution document or as a separate document. It is pr efered to get the client do this work due to ownership as their internal stakeho lders will have to sign off. 4.1 ----> Client says this is what we have in V2 and we demo what we have in V3, Client came with the gaps or issue. 4.2 ----> We discuss end to end impact here because V2 is already implemented an d we have to reuse most of the interfaces 4.3 ----> Data migration 4.4 ----> New interfaces are identified N.B. End result is that we involve in solutioning. ---------- Client Business Sign-off --------5 -> SOW signed off and client has agreed to the scope and costing ---------- Development and Testing --------6 -> Development (Host/IB/Interfaces) 6.1 ----> Weekly review of issues raised in Jira e.g. say the client has to pass additional field in an interface to the Third Party system now this will impact us therefore, client will log an issue in Jira and let us know so that we can t ake correction action 6.2 ----> Simlarly if you cannot deliver something previously agreed or there is a design change then go back to the client (via Jira) and negotiate 6.3 ----> Identify Change requests 7 -> We start the integration very early which means we share inputs and outputs from different systems or if we have a test system then we integrate with it st raight away in the development phase. 7 -> Arrange for Demos especially for change requests 8 -> Change Requests - Documentation, Sign-off, Development and testing 9 -> SIT phase - deployment -> BAs may be required to supply with clarifications and also attend the weekly meeting 10 -> UAT phase - deployment -> BAs may be required to supply with clarification s and also attend the weekly meeting 11 -> Go live - on call support

New implementation - N.B. At every stage you should be aware of what is billable and what is not in which case alwyas ask the Project Manager on your side. ------------- Preparation ------------------1 -> SOW is supplied. Could have a phased approach. 2 -> Peel through the SOW so that you can create workshop approach (WSA) documen ts 3 -> Prepare for requirements gathering - Setup Demo and prepare a Slide Pack. G o with the slide pack and demo when required ------------- Preparation & Solutioning ------------------4 -> During the requirement you are supposed to cover all SOW items and identify

what your system has or not. Ask wquestions for what you do not have to underst and what is expected to be delivered 5 -> Also for exsiting functionality identofy what you do not have or where ther e is a change 6 -> At the end of esch session Minutes will be documented and supplied to the a udience. Next day the first activity will be to disucss and close previous day's minutes. 7 -> After the sessions, BAs will write the Requirements document and supply it to other vendors or whoever is affected. This is done through Project Management Office. 8 -> After the sessions there will be a solutioning phase where each of the requ irements documents will be discussed in detail for technical and functional feas ibility. If something cannot be delivered then we go back to the client. ---------- Client Business Sign-off --------9 -> SOW signed off and client has agreed to the scope and costing ---------- Development and Testing --------10 -> Development (Host/IB/Interfaces) 10.1 ----> Weekly review of issues raised in Jira e.g. say the client has to pas s additional field in an interface to the Third Party system now this will impac t us therefore, client will log an issue in Jira and let us know so that we can take correction action 10.2 ----> Simlarly if you cannot deliver something previously agreed or there i s a design change then go back to the client (via Jira) and negotiate 10.3 ----> Identify Change requests 11 -> We start the integration very early which means we share inputs and output s from different systems or if we have a test system then we integrate with it s traight away in the development phase. 12 -> Arrange for Demos especially for change requests 13 -> Change Requests - Documentation, Sign-off, Development and testing 14 -> SIT phase - deployment -> BAs may be required to supply with clarification s and also attend the weekly meeting 15 -> UAT phase - deployment -> BAs may be required to supply with clarification s and also attend the weekly meeting 16 -> Go live - on call support