Qualification gates
A gate closes a phase. The team shows evidence for each checklist item. The steering group then approves, approves with conditions, or rejects.
This page applies to every stage.
IDK templates: IDK-08
Page in the app: /p/{projectId}/gates
From checklist to decision
A rejected gate can be reopened for another round.
- Work the checklist. Each item gets an owner and a link to evidence.
- Request the decision. The project manager recommends.
- Steering group decides. Approve, approve with conditions, or reject.
- Conditions. Each condition becomes a linked issue with an owner, a date and a checker.
- Next phase. The baselines in force are saved with the decision.
Each gate closes one phase.
- Initiate project. Both teams start. You set up the plan, the scope and the controls.
- IDK templates: IDK-01, IDK-02, IDK-03, IDK-04, IDK-05, IDK-06, IDK-07
- Gate: Project initiated
- Confirm prototype. You build key processes on customer sample data and confirm the solution scope.
- IDK templates: IDK-09, IDK-10
- Gate: Solution confirmed
- Establish solution. You finish design, build and tests. The phase ends with acceptance testing.
- IDK templates: IDK-11, IDK-12, IDK-14, IDK-15, IDK-16, IDK-17, IDK-18
- Gate: Solution established
- Implement solution. You train users, rehearse the cutover and pass the operational readiness test.
- IDK templates: IDK-19, IDK-20, IDK-21
- Gate: Go live authorised
- Go live. You run the cutover, retire the old system, hand over to support and close the project.
- IDK templates: IDK-20, IDK-22, IDK-24
- Gate: Go live complete
- Maintained after go-live. The system stays current through service and release updates.
- IDK templates: IDK-23
Project manager guide
Close each phase with evidence the steering group can trust.
- Work the checklist.
- Do now: Give each item an owner and link the evidence that proves it.
- Why: The steering group decides on evidence, not on opinions.
- The app checks: Items that do not apply start as not applicable, such as the multi-site item in a single-site project.
- Next: Check the readiness tabs.
- Check readiness.
- Do now: Open the readiness tab of each register that an item names. Close the blocking gaps it lists.
- Why: A tab says ready, blocked or cannot assess before you claim the evidence.
- The app checks: Not applicable means the project has no objects of that kind. It does not block the gate.
- Next: Request the decision.
- Request the decision.
- Do now: Start the review when no item is untouched. Add your recommendation.
- Why: The decision opens the next phase.
- The app checks: A project manager recommends and then the steering group chair decides. The decision may ask for a recent multi-factor sign-in.
- Next: Track each condition as an issue until it is closed.
How to do it
- Open the gate. See the checklist and what is still untouched.
- Add evidence. Link the document, test result or decision that proves the item.
- Check readiness. Open the readiness tab of a register to see whether its evidence is ready to claim for an item.
- Request the decision. You can only ask when no item is untouched.
Good to know
- Conditions do not block the next phase. They are tracked as issues until closed.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: