The key checkpoints for a Governance Track are described here: Major CheckpointThe major checkpoint concluding a Governance Track is customer acceptance. Customer AcceptanceLead Advocacy Group: Product Management A customer acceptance checkpoint signifies that the customer(s) is satisfied with what was delivered as per the previously defined customer acceptance criteria. To achieve this checkpoint, customers usually require prior acceptance from users, operations, and site owners; delivery of a project closeout report; and sometimes administrative closure of a project. This checkpoint signifies the conclusion of a project, even though a solution might not be fully deployed yet. This situation occurs when an operations team assumes responsibility for the remainder of a solution deployment and is confident and capable enough to no longer need project team support. Interim CheckpointsThe interim checkpoints for a Governance Track are project charter completed, project kicked off, user acceptance, operations acceptance, and customer acceptance, as depicted in Figure 12-1. Figure 12-1. Governance Track checkpoints
User AcceptanceLead Advocacy Group: User Experience This interim checkpoint signifies that the stakeholders formally acknowledge that a representative population of users, through various feedback mechanisms (e.g., user acceptance testing, surveys), have assessed a solution and concur that it meets their needs and is sufficiently usable. This checkpoint is typically achieved in a Stabilize Track in concert with the achievement of a user acceptance testing completed interim checkpoint. However, some organizations choose to tie the achievement of this checkpoint with the affirmative feedback received from surveying a sample user population once a solution is deployed. Operations AcceptanceLead Advocacy Group: Release/Operations This interim checkpoint signifies that an Operations team formally accepts responsibility for a solution. Typically, this checkpoint occurs in a Deploy Track when operations and support teams are ready, willing, and capable of assuming responsibility to finish deploying a solution. |