If any process in this document conflicts with any document in NODIS, this document shall be superseded by the NODIS document. Any reference document external to NODIS shall be monitored by the Process Owner for current versioning.
The purpose of this system level procedure (SLP) is to establish a consistent and documented method for collecting and disbursing Success Stories related to the work performed within the NASA IV&V Program.
The goals of Success Stories collection and disbursal are to:
Capture major accomplishments and their added value to the NASA IV&V Program
Support the NASA IV&V Program’s strategic goals and objectives, and continually highlight the best products, processes, and services provided by the Program
This SLP applies to all NASA IV&V civil service and contract employees across all functional organizations.
Definitions and Acronyms
Official NASA IV&V Program roles and terms are defined in the Quality Manual. Specialized definitions identified in this SLP are defined below.
The Screening Lead is the Strategic Communication Office (SCO) Lead or a designee who assesses the originality and completeness of a submission to the Success Stories Database.
The Screening Team comprises representatives from the Strategic Communication team and applicable subject matter experts from the associated functional area(s) to verify the accuracy and completeness of a Success Story submitted to the database.
Success Stories Annual Review
The Success Stories Annual Review is a review performed annually to assess the need for process improvement and ensure that the needs of the NASA IV&V Program are being met. If changes are needed, documentation will be revised, and staff will be informed.
Success Stories Database
The Success Stories Database is a Knowledge Management System (KMS) data repository that manages Success Stories for the NASA IV&V Program. It is located at http://lessons.ivv.nasa.gov/success/home.asp.
A Success Story is the accumulation of highlights from a work effort in regard to engineering findings, program successes, and management achievements. A Success Story provides an explanation of an accomplishment (or group of accomplishments), the results of the accomplishment, and the value added to internal/external customers. A Success Story can be (but is not required to be) tied to NASA-derived technology or supported by the Office of Safety and Mission Assurance (OSMA).
The following diagram depicts processes described in this document, and the responsibilities and actions that shall be performed by process participants or their designees. Any information supplemental to the depicted process will appear after the diagram.
The Success Story Originator shall draft a Success Story in the Success Stories Database for review by the assigned Screening Lead.
If the Success Story originates from work performed in the IV&V Office, the following information must be captured:
Project – The IV&V Project that is associated with the Success Story
Safety Category – The type of safety enhanced as described by the content of the Success Story (e.g., mission, crew, and/or public safety)
Additionally, the Success Story Originator must compose a paragraph or set of paragraphs that addresses the following three elements:
Accomplishment – What work has been performed? On what work has significant progress been made?
Result – What are the direct results, findings, or outcomes of the accomplishment?
Value Added Statement – What is the benefit of the accomplishment to the Project/Program/Agency?
These three elements will be combined to form the overall Success Story. To ensure that the Success Story is effective and applicable for future use, the Success Story Originator should aim to minimize the use of acronyms, ensure that pronouns and objects are clear, and write in a conversational language that uses active verbs to convey the meaning of the success as a story.
If the Success Story Office/Group falls under the IV&V Office, the Success Story Originator shall fill out the “Project” field to indicate what IV&V Project is associated with the Success Story.
Additionally, if the Success Story falls under the IV&V Office, the originator shall select any or all of the safety categories to which the Success Story relates.
Once the Success Story is drafted and entered into the Success Stories Database, the Screening Lead is notified that the Success Story needs to be assessed. The Screening Lead will coordinate efforts with the Screening Team members to:
Ensure that the Success Story is factually accurate
Ensure that a similar Success Story does not already exist in the database
Success Stories that are approved will be maintained in the Success Stories Database.
The Screening Lead shall approve or reject the draft Success Story.
Approve – Upon review of the Success Story and assessment phase, the Screening Team shall determine if the Success Story is appropriate for documentation into the Success Story database.
Reject – Upon review of the Success Story and assessment phase the Screening Team can reject the Success Story due to duplicate information, or non-conformance. The Screening Lead shall notify the Originator for possible resubmission.
Database searches may be run anytime by any user with access to the database.
Any metrics associated with this SLP are established and tracked within the NASA IV&V Metrics Program.
The following records will be generated or updated and filed in accordance with this SLP and IVV 16, Control of Records, and in reference to NPR 1441.1, NASA Records Retention Schedules.