7.
Build on Proven Project Management Practices <ul><li>Establish and maintain a plan </li></ul><ul><ul><li>If you don’t know where you are going, you will probably end up where you don’t want to be </li></ul></ul><ul><li>Engage relevant stakeholders </li></ul><ul><ul><li>Instituted weekly coordination working group </li></ul></ul><ul><li>Track progress </li></ul><ul><ul><li>Schedule, task list tracked to closure </li></ul></ul><ul><li>Integrated Management </li></ul><ul><ul><li>Software Quality Assurance is your friend </li></ul></ul><ul><li>Risk Management </li></ul>

9.
Extend Software Development Activities to include Systems Engineering <ul><li>Emphasize and build interfaces to Program and Software Systems Engineering groups </li></ul><ul><ul><li>Program Systems Engineering acknowledged responsibility for requirements allocation and acceptance of software baselines </li></ul></ul><ul><ul><li>Software Systems Engineering maintained requirements evidence books </li></ul></ul><ul><ul><li>Project documented transfer of artifacts and completion of milestones </li></ul></ul><ul><li>Encourage all trade studies to use the DAR methodology </li></ul><ul><li>View the project as a system, not a collection of components </li></ul>

12.
Lessons Learned - 1 <ul><li>Process group cannot do it all </li></ul><ul><ul><li>Flow down of information and training essential to implementation </li></ul></ul><ul><li>Take full advantage of Organizational resources </li></ul><ul><ul><li>Presentations by Process Assessment Organization lead clarified principles and showed top management commitment </li></ul></ul><ul><li>Dig Early and Often </li></ul><ul><ul><li>Appeal to project people to save evidence - especially emails </li></ul></ul><ul><ul><li>Need to document verbal orders </li></ul></ul><ul><li>Training is Essential </li></ul>

13.
Lessons Learned - 2 <ul><li>Timelines are appropriate for communicating expectations of urgency, but they must be realistic </li></ul><ul><ul><li>Identifying the gaps and adjust for changing strategy </li></ul></ul><ul><ul><li>Allow adequate time to create, review and update documents, evidence notebooks, train participants, audit products and processes </li></ul></ul><ul><ul><li>Do peer reviews, including an informal appraisal </li></ul></ul><ul><li>Address resistance to change </li></ul><ul><ul><li>“I thought the organization did that.” </li></ul></ul><ul><ul><li>“Our customer won’t let us do that.” </li></ul></ul><ul><ul><li>“Why aren’t these projects included in the appraisal?” </li></ul></ul><ul><ul><li>“I want to do CMMI – I just don’t want to change our process.” </li></ul></ul>Whining