Project Gap Analysis

One can find out the viability of a program based on the team’s capabilities, sometimes referred to as “measles” chart. We designed it to match all the primary requirements of the program against the team’s capabilities (prime plus up to 24 team members). 

Once satisfied that the team capabilities are accurate and the requirements reflect the needs of the Client, matching the team capabilities to execute the requirements.

Note that the requirements identified are generated by parsing a Request for Information (RFI), Sources Sought or a Draft Request for Proposal (DRFP) or Draft Performance Work Statement (DPWS), perceived through discussion with the Client (contracts officer, technical lead, program manager, program executive, and other sources) prior to the release of the solicitation. Its principal use is in building a solution and assembling a team to pursue the opportunity.

The gap analysis delineates each of the requirements and who on the team can contribute to the solution defined by that requirement. An important aspect of gap analysis is identifying what needs to be done in a project.

 We compose typical gap analyzes of three distinct sections:

1. Identify a future state where we meet 100% of the requirement.
2. The current state that refers to each team member's capability to support the requirement or not.
3. Finally, delineate the next actions necessary to achieve 100%, if possible.

Status here should influence the bid/no-bid decision-making process.