Guide: phase 3, Establish solution
You finish design, build and tests. The phase ends with acceptance testing and the Solution established gate.
This page applies to the Establish solution stage.
Project manager guide
Deliver a built and tested solution that matches the approved scope, with trial data loaded and guides written.
- Approve the specifications.
- Do now: Open Specifications. Write one for each integration and modification, and one for configuration and reports. Get each approved before the build starts.
- Why: Developers build from an approved text, so later disputes have a reference.
- The app checks: A CRIM object cannot be specified before its specification is approved. The gate asks for complete specifications.
- Next: Build and test.
- Build and unit test the CRIM objects.
- Do now: Move each CRIM object through build and test. Build and test each interface end to end.
- Why: Untested custom objects are the main source of late defects.
- The app checks: Accepting a CRIM object needs test evidence. A failed test sends it back to build and creates a defect.
- Next: Prepare the data.
- Run the migration cycles.
- Do now: Open Data migration. Approve the plan, run at least one trial load and review the result against the tolerance.
- Why: Each cycle should find fewer issues than the one before.
- The app checks: An object may set its own tolerance, and it needs a reason before its mapping is approved.
- Next: Write the guides.
- Write and verify the step-by-step guides.
- Do now: Open Step-by-step guides. Write the key processes and let a second person follow each guide.
- Why: Testers, trainers and support all use the same guides.
- The app checks: Only released guides go into the document pack.
- Next: Prepare acceptance testing.
- Prepare acceptance testing.
- Do now: Open Testing. Write the scenarios, check the entry criteria and plan the cycle, the window and the environment.
- Why: Acceptance testing starts only when the build is ready to test.
- The app checks: Open defects of a blocking severity stop acceptance. The readiness tab names the gaps.
- Next: Review risks and scope.
- Review the risks and reconcile the scope.
- Do now: Review open risks and issues with their owners. Compare what you built with the approved scope.
- Why: The steering group should see differences before the gate, not at it.
- The app checks: Any difference to the baselines needs a change request.
- Next: Close the gate.
- Close the gate.
- Do now: Open the Solution established gate. Link the evidence for all 11 items and request the decision.
- Why: This gate opens the training and cutover work of phase 4.
- The app checks: You can ask only when no item is untouched. The steering group chair decides after your recommendation.
- Next: Continue with the guide for the Implement solution stage.
Related topics
- Specifications
- Testing
- Data migration
- Step-by-step guides
- Defects
- Qualification gates
- Guide: phase 4, Implement solution
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: