C3 - Make a go/no-go decision
It’s time for the cyclic go/no-go decision. Before making the decision, each hat-wearer expresses their concerns:
Are the targets and expectations still realistic and achievable?
Is the existing understanding of the project still suitable for end users?
Is it still possible to meet the requirements?
Is the project goal still achievable?
Is the project still justifiable?
Is the project still the best investment of our resources at this time?
After this, the person or group responsible for the go/no-go decision (set in A1) makes a decision. The decision and its related information are recorded on a card on the Integrated Project Board.
When a project loses its justification and it doesn’t make sense to continue it anymore, a no-go decision will be expected, in which case the team should archive the documents, stop the project, and announce its cancellation. If a project has a dynamic scope and the latest output seems to be enough, a no-go option shouldn’t be used to stop it, but you should review and close the remaining deliverable cards on the Integrated Project Board as canceled ones and proceed normally to tie up the loose ends and close the project.