Scoping
Set out the work, responsibilities and terms so everyone understands how the engagement will proceed. Discovery then works through the source-specific detail.
A shared understanding of the engagementHow an engagement works
From scoping
to production.
Report by report.
We scope the work with you, arrange access and work through the records with your team. Discovery and validation repeat for each report type in scope.
- 01ScopingAgree on the scope, responsibilities and terms.
- 02AccessArrange data access, files and required clearances.
- 03DiscoveryUnderstand the source and configure each report type.
- 04ValidationReview the records, resolve findings and recheck changes.
- 05ProductionMake the approved reports available to the intended users.
Repeat Discovery and Validation for each report type in scope.
Before the report work
Scope the work.
Arrange access.
The engagement establishes responsibilities. Access gives the implementation team the source material it needs to begin discovery.
Access
Arrange the agreed data access or extracts, associated files and required clearances. Identify the people who can answer questions about the source and its environment.
Source material and the people who know itThe work, report by report
Build something your team
can check in context.
Review a configured report with its fields, codes and relationships. Specific findings give the implementation team something concrete to investigate and revise.
Discovery
Examine the source data, report layouts, codes and relationships. Configure the report type in LiftShift Records so your team can review the information in context.
Validation
Your reviewers check records in the application against the source. We investigate findings, revise the configuration and recheck the results together.
Repeat Discovery and Validation for each report type in scope.Work through findings and recheck changes before the approved report moves into production.
From a finding to a checked changeFictional records
From a finding to a checked changeFictional records
This example is laid out for a wider screen.
Production
Put the approved
reports to work.
Put the agreed records into use in the chosen hosting environment, with access and operating responsibilities clear. The legacy-retirement plan also accounts for any remaining dependencies.
The archive can be part of a replacement project or help an organization that has already moved systems. The customer decides when the old application can retire.
Hosting, access and responsibilitiesStart with your situation
What still depends on the old system?
Tell us what is changing and what people still need to do. You don’t need a source inventory to begin.