metis-gap-analysis

Pre-delivery gap analysis is a validation step that identifies hidden intentions, ambiguities, missing criteria, and edge cases in a project plan before final approval. It ensures comprehensive coverage by injecting discovered gaps directly into the plan for revision.

To validate a project plan before delivery, run a gap analysis step to uncover overlooked elements and edge cases. The plan author must define clear objectives, scope, and criteria, then review the injected gaps and clearance checklist for final approval.

You need to run gap analysis during the project planning phase, specifically after an initial plan is generated but before delivering it for user approval. This pre-delivery timing catches overlooked implementation elements early.

Gap analysis checks a project plan for hidden intentions, ambiguities, missing criteria, over-engineering, and edge cases. It provides a clearance checklist to verify that the plan author defined clear objectives and scope, ensuring thorough validation.

Yes, you need to define clear objectives, scope, and criteria before running plan validation. Gap analysis requires these predefined elements from the plan author to effectively uncover hidden ambiguities and ensure comprehensive coverage before delivery.

A limitation of gap analysis for plan revision is that it cannot compensate for poorly defined objectives or missing scope. It requires the plan author to establish clear criteria beforehand, otherwise the validation cannot effectively uncover hidden edge cases.