...
Customer requests a CSM or Sales Rep or adds an issue in Jira
Integration Team determines that this is a CR. This means that there will be a cost implication for FT
CSM/Sales Rep informs the customer and Amardeep that this is going to be a Change Request involving a cost component. Get’s in-principle approval from the client & Amardeep.
CSM/Sales Rep prepares a Change Request Document to capture the requirement
Integration Team does impact analysis and determine what code changes are required
Add solution approach, effort in person-days, tentative timelines to CR document
CSM adds cost based on agreed billing rates with the customer
CSM gets approval from Amardeep. CC Sumesh, Mohit
CSM gets approval from customers by mail
CSM creates a Change Request in Jira giving a link to the CR document for tracking progress
CR in Jira must be created on behalf of the customer rep. CC Sumesh and Amar on Jira CR
CSM takes care of customer communications. Following are the implementation steps, mostly driven by the integration team
Integration Software Engineer does further assessment and provides a firm Due DatePlanned Interfaces are defined and documented including APIs, process steps, schemas,
Integration Software Engineer creates a detailed API document (or enhances an existing one) covering
Planned Interfaces
APIs
process steps
schemas
request payloads,
responses, etc
Integration Software Engineer shares Interface document with customer and CSM gets an approval from the customer
Integration Software Engineer
develops and continuously updates statuses in Jira so that customer knows the progress
Dev Ops Deploys to QA
FT QA does internal testing
Dev Ops deploys to Integration server
Customer does Integration Testing & User Acceptance Testing, Customer sends UAT sign-off on Jira CR Issue
Dev Ops deploys change to production server
The customer goes live with the change. CSM to followup and get go-live sign-off
...