The methodology maintains the flexibility to adapt to customer needs and practices. It is not a strict procedure, but rather a roadmap to be modified to fit the dynamics of each implementation. However, it defines mandatory elements of the expected implementation management standards and processes.

Implementation will be executed on Agile development methodology, that would consist of various sprints, primarily categorized into Inception or Sprint-0, Development sprints (Sprint 1 through n), Tail Sprint.

The sub-phases within the implementation phase are described below.

The solution architect will work on creating the solution architecture blue-print that would focus on system integration, security, performance and other non-functional aspects of the solution. The business analysts will work with customer business users to go through requirements around content management, workflow and other requirements to create Business Requirements Document (BRD). Indicative scope for each development sprint along with a master test plan will also be created during the inception phase. Business requirements and non-functional requirements as outlined in the solution blue-print, will be created as user stories in the Agile tracking tool as backlog.

UX design principle will be finalized during inception phase well to have better user adoption of the solution. A dedicated due diligence phase on detailing the integration points requirements and high level design will be conducted during the inception phase, which would help finalize the number of development sprints required to implement the complete scope.

In addition to the application specific activities, the infrastructure needed for various environments is planned during inception phase, with at least DEV and TEST environments are usually built and delivered to the development teams prior to start of the development sprints.

A sprint level testing that includes functional, security, accessibility will be conducted prior to closure of the sprint. A sprint level business demo will be conducted to gather business user feedback on the functionality developed, which may add additional user stores in the backlog.

All remaining environments including PROD are built and delivered to the project team prior to completion of the last development sprint.

Similarly end to end performance, security, accessibility, browser compatibility, device testing are conducted prior to going for Go-Live approval. The production deployment playbook and other go-live checklist items are verified, signed-off from required parties prior to the go-live date.

Transition to ongoing support team, user guide, training activities are carried out throughout development and tail sprints.

Some key project SME resources are available for incident resolution support for a period up to 60 days post go-live (stabilization period), that Ongoing Managed Service team can take help from as required.

Apart from production incident and SLA management, up to 6 minor releases per year are included in scope of services. The minor releases include any code fixes and regulatory changes needed. The Efficiency Platform has up to 3 major releases in a year that will include functional enhancements to the core product. Should customer decide to implement a major release of the Efficiency Platform, NTT DATA core support manager will work with customer stakeholders to estimate and plan.