Attachment 14 Project Briefing Guidance.pdf

Navy ManTech Program

REV K OCT24

Project Briefing Guidance

Attachment:

1. Project Briefing Template

A. PURPOSE

The Navy ManTech Program has been having a real impact on the affordability of key investment platforms. In order to continue to fund projects that will implement and have an impact on affordability and capability acceleration, project briefings for program review meetings have been standardized.

This guidance includes a presentation template and instructions regarding the desired content of presentations. Different content is requested depending on the maturity of the project. Early in the project, introductory project information, specific technical goals, technical approach, etc. should be emphasized. As the project matures, the emphasis should be on project status, identified risks and other issues, and risk mitigation plans. As the project nears completion, the emphasis should be on implementation. In all cases, the focus should be on transition / implementation noting the current status / progress that has taken place the last 6-12 months (especially changes since the last briefing);

the risk assessment and management of any issues that need to be mitigated; and near-term plans (especially in terms of risk management) highlighted.

All projects have an inherent risk of not implementing. It is important that ManTech, the Centers of Excellence (COEs), industry, Program Offices, PEOs, etc. recognize the risk early, understand it, and develop plans to manage it throughout the project execution phase. The program review processes have been revised to emphasize the importance of implementation by recognizing project risks to implementation upfront and then assessing and managing these risks through project execution.

Note: Project briefings are not required for 6.2 Navy Manufacturing Applied Research projects.

B. REQUIRED TIMELINE

Briefings for program review meetings will be prepared in PowerPoint in accordance with this guidance.

C. PROCESS / APPROVAL CYCLE

No Official Project Briefing Call: COEs will prepare briefings as required and specified in their respective contracts and upload them to the applicable folder of the Project tab of the Navy ManTech Projects Database (NMPD), if available.

If the NMPD is unavailable, COEs will use one of the acceptable submission methods shown below to submit the project briefing, and the Navy ManTech Support Team will upload the brief to the database:

Acceptable Submission Methods:

DoD Safe – https://safe.apps.mil/ COE File-Sharing Site E-mail with encryption

D. FORMAT

As noted in Section A above, all Project Briefings should use the attached template; briefings should be developed in PowerPoint. The template is divided into two sections, the main section (slides 1–10) and a backup section (slides 12–14). The slides to be included in a briefing and the slides to emphasize depend on the maturity of the project as detailed below. In all cases, transition / implementation and the risks associated with transition / implementation should be strongly emphasized and a project risk assessment must be included.

1. New projects that have either never been briefed or perhaps briefed just once should focus on a good overall description of the project, including project objective, goals, anticipated achievements, the importance to the platform, plans for transition / implementation, and the associated risk assessment. For these projects, slides 1–10 and 12–14 should all be briefed. Do not brief slide 11.

2. For a project that has been briefed more than once at earlier program reviews, the briefing should focus on project status and progress in the past 6–12 months, changes to project scope / approach, issues, and, most importantly, identified risks to implementation and risk mitigation plans. When briefing slides 2–5, point out any changes since the previous review; these slides should not be briefed in detail after the first program review.

The main emphasis should be on slides 6–10, focusing on what has occurred in the past 6– 12 months, the overall status, and problems, if any. The risks should be clearly identified indicating what action has been or will be taken to mitigate each risk. Note that slides 12– 14 should be included as backup in all briefings.

3. Partial implementations that have occurred during any stage of a project should be specifically highlighted in the briefing regardless of the maturity of the project.

Risks will be presented in each Project Briefing in accordance with the current version of the Implementation Risk Assessment Process Guidance. Refer to the current Risk Factor Definitions for “Red,” “Yellow,” and “Green” and a more in-depth understanding of the appropriate risk color designation.

All Risk Factors for a specific Project Category should be included. If a Risk Factor is not relevant to the project, it should be listed and the risk factor cell should be “grayed.”

NOTE: For all projects that have been assigned a “Red” rating during any previous program review, an extra slide must be included with details of the Risk Mitigation Plan as well as the progress against the steps in the plan.

E. REVISION REQUIREMENTS AND FILE NAME

1. Revision Requirements:

All Navy ManTech Project Briefings should include the official Navy ManTech project number, complete project title, and the specific meeting title and date in the left footer as shown in the template. All briefings should be prepared using Microsoft PowerPoint.

2. File name convention:

File names for Project Briefings should be in the following format: {COE acronym} PB {official project number} {complete official title of project} {MMMYY}.

i.e., NMC PB S2397 Pipe Assembly Installation Improvement Methods AUG12.pptx

Attachment 1: Project Briefing Template