1、Public Lessons Learned Entry: 4580 Lesson Info: Lesson Number: 4580 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Early Implementation of a Change Management Process Abstract: A change management process should be developed at program/project inception and implemented with rigor.
2、An automated system for change management would be best. Description of Driving Event: In the Constellation Program (CxP), an unstructured change management process drove increased costs and impacted schedules. Because of the change management process immaturity in CxP, unfunded requirements were le
3、vied on the Ground Operations Project, and costs were not adequately quantified. Early efforts at Change Management were accomplished by a manual process and not an automated tool, which adds the risks introducing errors. Lesson(s) Learned: Programs should have a robust change management process fro
4、m inception that precludes unfunded requirement flow-down. Recommendation(s): Develop and implement a strong change management process that controls and evaluates all impacts of proposed changes (cost schedule, and risk). Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson:
5、 N/A Mission Directorate(s): Exploration Systems Additional Key Phrase(s): Program Management.Business Processes Program Management.Organizational Planning Program Management.Program planning, development, and management Program Management.Configuration Data Management Additional Info: Project: Constellation Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: Approval Date: 2012-11-08 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
