REG NASA-LLIS-4581-2012 Lessons Learned - Programs Need A Robust Change Request (CR) Pipeline Tool.pdf

1、Public Lessons Learned Entry: 4581 Lesson Info: Lesson Number: 4581 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Programs Need A Robust Change Request (CR) Pipeline Tool Abstract: The Constellation Program (CxP) developed a tool to alert Projects within the Program of upcoming Ch

2、ange Requests (CRs). This tool was known as the CR pipeline tool. Management of Constellation Program CR Pipeline tool utilization needs to be improved in order to ensure traceability for all CRs entered into the tool, to ensure proper flow-down actions related to assessing the CR, tracking CR withd

3、rawals , and to provide accurate change management reports and metrics. Withdrawn CRs should never just be deleted; a record of withdrawal should be retained. Description of Driving Event: The CR Pipeline tool was used to prepare a CR Look Ahead Chart for the weekly Project Review Board (PRB), resea

4、rch documents and for tracking and statusing flow-down of documentation and upcoming CRs. The CR Look Ahead chart is used to help the KSC Ground Operations Project plan the assessments of upcoming Change Requests. There is no history (or retention record) on each CR in the pipeline tool (i.e., dates

5、, Change Package Manager, CR withdrawals, etc.). The lack of proper tracking of CRs in the pipeline tool results in lack of accountability for CRs, inaccurate metrics, and wasted resources due to numerous emails for inquiries, phone calls, etc. to status the CRs. The pipeline tool does not properly

6、support the change management function. Lesson(s) Learned: Programs must ensure stability, traceability, and accountability for tools used to manage Change Requests. A uniform tool for use across the Program to allow projects to plan for assessing upcoming changes is a good idea but the tool must ac

7、curately reflect and account for CR withdrawals and changes in CR due dates in order to support Change Management. Recommendation(s): Programs must establish a uniform change tracking and planning tool that provides accurate tracking of upcoming CRs, including providing status on modifications or wi

8、thdrawals of CRs. Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: N/A Mission Directorate(s): Exploration Systems Additional Key Phrase(s): Program Management.Configuration Data Management Additional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Project: Constellation Approval Info: Approval Date: 2012-11-02 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-