generated from cotes2020/chirpy-starter
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
801f9a4
commit e8a83aa
Showing
1 changed file
with
80 additions
and
73 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,113 +1,120 @@ | ||
| --- | ||
| title: 'Part 2: Implementation' | ||
| - - - | ||
|
|
||
| ## title: 'Part 2: Implementation' | ||
|
|
||
| layout: post | ||
| icon: fas fa-users-gear | ||
| order: 5 | ||
| toc: true | ||
| --- | ||
|
|
||
| {: .dark .w-75 .shadow .rounded-10 w='1212' h='668' } | ||
| {: .light .w-75 .shadow .rounded-10 w='1212' h='668' } | ||
| _The Implementation Project Lifecycle_ | ||
| *The Implementation Project Lifecycle* | ||
|
|
||
| #### Overall Timeline | ||
| - Project Pre-formulation | ||
| - Project Formulation | ||
| - Project Implementation | ||
| - Project Operations | ||
| - Project Closeout | ||
| - Solution Operations Handoff or Defunding (MO action) | ||
| - Solution Closeout (MO action) | ||
|
|
||
| * Project Pre-formulation | ||
| * Project Formulation | ||
| * Project Implementation | ||
| * Project Operations | ||
| * Project Closeout | ||
| * Solution Operations Handoff or Defunding (MO action) | ||
| * Solution Closeout (MO action) | ||
|
|
||
| ## The SNWG MO Program Plan | ||
|
|
||
| The SNWG MO Program Plan should have been shared with you as a part of your "Welcome to the SNWG" package. The purpose of this document is to provide a framework and governance to the operations of the Management Office throughout the Program and Project lifecycles. You may also click here for a [direct link to the SNWG MO Program Plan pdf](https://drive.google.com/file/d/1xe-rrKjwZZ7p0w39umL7nPdjCXmWwkUW/view?usp=sharing) | ||
|
|
||
| ### Why you care | ||
|
|
||
| While the SNWG MO Program Plan governs the overall process and actions of the SNWG MO, not all sections are relevant to our Projects. However, several key portions do directly impact the Projects overseen by the MO. It may not be necessary to read the entire document to understand the Office and its processes, but understanding these crucial parts is essential for the funding and ultimate success of your project. | ||
|
|
||
| ### What parts matter to you? | ||
| ### What parts matter to you? | ||
|
|
||
| Key parts of the SNWG MO Program Plan for the purposes of the Project Implementation Teams are: | ||
| - 5.1.2 Requirements on the SNWG Solution Projects | ||
| - 6.2 Solution Project Implementation Collaborations | ||
| - 6.3 SNWG MO SEP Collaborations | ||
| - 12.2 Solution Project Lifecycle | ||
|
|
||
| * 5.1.2 Requirements on the SNWG Solution Projects | ||
| * 6.2 Solution Project Implementation Collaborations | ||
| * 6.3 SNWG MO SEP Collaborations | ||
| * 12.2 Solution Project Lifecycle | ||
|
|
||
| ## Your Solution Project Plan | ||
| [Link to Template](https://docs.google.com/document/d/1hfbKXOta7htTs1RDtvpAXxBwu6QxuqnndGXOMkyM-UQ/edit) | ||
|
|
||
| | You fill out | We fill out | | ||
| | :-------------------------------------------------- | :-------------------------------------- | | ||
| | 2.3 Project Schedule/ Key Project Level Milestones | 2.5 Budget and Acquisition Approach | | ||
| | 2.4 Project Resources and Annual Cost Estimate | 3.2.1 PLR Compliance Matrix | | ||
| | 3.2 Project Requirements | 3.3 Strategy for Technology Transition | | ||
| | 4.1 Risk Management Strategy | 3.4 Project Reviews | | ||
| | 4.2.1 Open Science Data Management Plan | 4.3 Tailoring Approach | | ||
| | SNWG MO Systems Engineer | | | ||
| | SNWG MO Project Coordinator | | | ||
| [Link to Template](https://docs.google.com/document/d/1hfbKXOta7htTs1RDtvpAXxBwu6QxuqnndGXOMkyM-UQ/edit) | ||
|
|
||
| | You fill out | We fill out | | ||
| | :----------- | :---------- | | ||
| | 2.3 Project Schedule/ Key Project Level Milestones | 2.5 Budget and Acquisition Approach | | ||
| | 2.4 Project Resources and Annual Cost Estimate | 3.2.1 PLR Compliance Matrix | | ||
| | 3.2 Project Requirements | 3.3 Strategy for Technology Transition | | ||
| | 4.1 Risk Management Strategy | 3.4 Project Reviews | | ||
| | 4.2.1 Open Science Data Management Plan | 4.3 Tailoring Approach | | ||
| | SNWG MO Systems Engineer | | | ||
| | SNWG MO Project Coordinator | | | ||
|
|
||
| ## Decision Gates | ||
|
|
||
| ### What are they and why do we have them? | ||
| Each decision gate ensures that the project has properly investigated and developed the development, budgeting, and documentation appraoch required to move to the next phase in the project lifecycle for maximum return of value to both the funding sources of the project and the end user of Solution Product. | ||
|
|
||
| Each decision gate ensures that the project has properly investigated and developed the development, budgeting, and documentation appraoch required to move to the next phase in the project lifecycle for maximum return of value to both the funding sources of the project and the end user of Solution Product. | ||
|
|
||
| ### Authority to Proceed | ||
|
|
||
| The Authority to Proceed Decision Gate (AtP DG) is a focused review of the inital project documentation to determine the solution project’s readiness to proceed from Pre-Formulation to Formulation and document the decision. (SNWG MO Program Plan 12.2.1.6) | ||
|
|
||
| _The pre-formulation phase of a solution project starts after NASA learns about proposed SNWG activities in OMB’s funding request. Projects begin at this stage, but budget and scope adjustments can still be made until NASA receives and distributes funds (at the start of the fiscal year) and the project enters the formulation phase. Initiating solution projects at this stage allows pre-formulation activities to be carried out so that funds can be distributed to solution projects as soon as possible._ | ||
|
|
||
| - What you need to do before the ATP DG: | ||
| - Complete your preliminary Project Plan, which includes: | ||
| - [X] Notional OSS Objectives (How will your project adhere to Open Source Science principles during Solution Product development and operation?) | ||
| - [X] Notional SEP Plan (How will your project promote stakeholder engagemenet throughout the Solution Product development and operation?) | ||
| - [X] Outline your management approach (Team structure, partnerships, acquisition strategy, Milestone reviews Tip: Refer to team members by their ROLE thoughout the plan. Define the names associated with the role in a chart in supporting sections.) | ||
| - [X] Notional schedule (Tip: Use ranges and relative times, not exact dates i.e. "2 months after project signing" "2 years after project Implementation start" Do keep in mind the limitations of final funding dates.) | ||
| - [X] Resource requirements | ||
| - Project L1 | ||
| - PLR Compliance matrix | ||
| - [X] Solution Product Transition or Dissemination approach (Firm handoff plans are not required. Do include preliminary suppositions and potential handoff agencies or partners to be investigated throughout the Project lifecycle and borne to fruition by Project Closeout.) | ||
| - [X] Risk Management Strategy | ||
| - [X] Applicable Control Plans | ||
| - Required: | ||
| - Notional Open Source Data Management Plan (OSDMP) | ||
| - As needed and customized for the scope of the Project: | ||
| - CM Plan (internal note: what is CM?) | ||
| - System Security Plan | ||
| - Risk Development Plan | ||
| - [X] Notice to the SNWG MO of any external funding sources necessary for project success | ||
|
|
||
| - What you need to do during | ||
| - The Project Implementation Team presents the goals and status of their project ~15 - 20 mintues | ||
| - The SNWG MO leads a walkthrough of the Implementation-prepared preliminary Project Plan. Your team will address any questions and make note of actions to be taken to address any concerns about the Project Plan. | ||
|
|
||
| - What you need to do after | ||
| - Complete any outstanding action identified as blockers to signing the ATP DG Memorandum. | ||
|
|
||
| - Ultimate result: The Solution Project is authorized to proceed to the Project Formulation stage where the finer details of developing the Solution Product will be documented, the contractual agreement between NASA and the contracting Project organization is foramlized. | ||
| *The pre-formulation phase of a solution project starts after NASA learns about proposed SNWG activities in OMB’s funding request. Projects begin at this stage, but budget and scope adjustments can still be made until NASA receives and distributes funds (at the start of the fiscal year) and the project enters the formulation phase. Initiating solution projects at this stage allows pre-formulation activities to be carried out so that funds can be distributed to solution projects as soon as possible.* | ||
|
|
||
| * What you need to do before the ATP DG: | ||
| * Complete your preliminary Project Plan, which includes: | ||
| * [x] Notional OSS Objectives (How will your project adhere to Open Source Science principles during Solution Product development and operation?) | ||
| * [x] Notional SEP Plan (How will your project promote stakeholder engagemenet throughout the Solution Product development and operation?) | ||
| * [x] Outline your management approach (Team structure, partnerships, acquisition strategy, Milestone reviews Tip: Refer to team members by their ROLE thoughout the plan. Define the names associated with the role in a chart in supporting sections.) | ||
| * [x] Notional schedule (Tip: Use ranges and relative times, not exact dates i.e. "2 months after project signing" "2 years after project Implementation start" Do keep in mind the limitations of final funding dates.) | ||
| * [x] Resource requirements | ||
| * Project L1 | ||
| * PLR Compliance matrix | ||
| * [x] Solution Product Transition or Dissemination approach (Firm handoff plans are not required. Do include preliminary suppositions and potential handoff agencies or partners to be investigated throughout the Project lifecycle and borne to fruition by Project Closeout.) | ||
| * [x] Risk Management Strategy | ||
| * [x] Applicable Control Plans | ||
| * Required: | ||
| * Notional Open Source Data Management Plan (OSDMP) | ||
| * As needed and customized for the scope of the Project: | ||
| * CM Plan (internal note: what is CM?) | ||
| * System Security Plan | ||
| * Risk Development Plan | ||
| * [x] Notice to the SNWG MO of any external funding sources necessary for project success | ||
| <br> | ||
| * What you need to do during | ||
| * [x] The Project Implementation Team presents the goals and status of their project \~15 - 20 mintues | ||
| * [x] The SNWG MO leads a walkthrough of the Implementation-prepared preliminary Project Plan. Your team will address any questions and make note of actions to be taken to address any concerns about the Project Plan. | ||
| <br> | ||
| * What you need to do after | ||
| * [x] Complete any outstanding action identified as blockers to signing the ATP DG Memorandum. | ||
| <br> | ||
| * Ultimate result: The Solution Project is authorized to proceed to the Project Formulation stage where the finer details of developing the Solution Product will be documented, the contractual agreement between NASA and the contracting Project organization is foramlized. | ||
|
|
||
| ### Formulation to Implementation | ||
|
|
||
| _After a successful ATP DG review and the establishment of a contract between the SNWG MO and the solution project, the formulation phase begins. This phase involves detailed planning for the implementation phase, including developing project control plans, finalizing the Project Plan, and establishing necessary agreements. Note that sometimes the formulation phase is brief, lasting just long enough to prepare for the Formulation to Implementation Decision Gate (DG)._ | ||
| *After a successful ATP DG review and the establishment of a contract between the SNWG MO and the solution project, the formulation phase begins. This phase involves detailed planning for the implementation phase, including developing project control plans, finalizing the Project Plan, and establishing necessary agreements. Note that sometimes the formulation phase is brief, lasting just long enough to prepare for the Formulation to Implementation Decision Gate (DG).* | ||
|
|
||
| - What you need to do before | ||
| - What you need to do during | ||
| - What you need to do after | ||
| * What you need to do before | ||
| * What you need to do during | ||
| * What you need to do after | ||
|
|
||
| ### Implementation to Operations | ||
| _After a successful Formulation to Implementation DG review, the project enters the implementation phase. Here, the planned activities are carried out as described in the Project Plan, following the scheduled costs and timelines. Periodic reviews and milestone assessments are conducted as outlined in the Project Plan. The implementation phase concludes either by moving into the operational phase or, for projects without an operational phase, by completing closeout activities like archiving data/information and undergoing a Project Closeout DG review._ | ||
| ### Implementation to Operations | ||
|
|
||
| - What you need to do before | ||
| - What you need to do during | ||
| - What you need to do after | ||
| *After a successful Formulation to Implementation DG review, the project enters the implementation phase. Here, the planned activities are carried out as described in the Project Plan, following the scheduled costs and timelines. Periodic reviews and milestone assessments are conducted as outlined in the Project Plan. The implementation phase concludes either by moving into the operational phase or, for projects without an operational phase, by completing closeout activities like archiving data/information and undergoing a Project Closeout DG review.* | ||
|
|
||
| * What you need to do before | ||
| * What you need to do during | ||
| * What you need to do after | ||
|
|
||
| ## Co-design/Co-production in the Implementation Phase | ||
| - what is expected of the Project team | ||
| - what is expected of the Stakeholders | ||
|
|
||
| * what is expected of the Project team | ||
| * what is expected of the Stakeholders | ||
|
|
||
| ## Open Source Science (OSS) in the Implementation Phase | ||
|
|
||
| <!-- markdownlint-capture --> | ||
| <!-- markdownlint-disable --> | ||
| > The Satellite Needs Working Group Management Office strongly encourages all SNWG Implementation team members take the time to enroll in and complete [NASA's Transform to Open Science (TOPS) OSS 101 course](https://nasa.github.io/Transform-to-Open-Science/). | ||
| {: .prompt-tip } | ||
|
|
||
| <!-- markdownlint-restore --> | ||
| > {: .prompt-tip } |