120 likes | 228 Views
CMMI Approach & Implementation. Mike Knuppel 03/20/2006. Basic Infrastructure Needs. CIO / CTO Positions Created – early 2001 Governance Model Implemented – two tier (tech / policy) PMO Created - late 2002 Development of IT Strategic Plan Established project management strategic goal
E N D
CMMI Approach & Implementation Mike Knuppel 03/20/2006
Basic Infrastructure Needs • CIO / CTO Positions Created – early 2001 • Governance Model Implemented – two tier (tech / policy) • PMO Created - late 2002 • Development of IT Strategic Plan • Established project management strategic goal • Implement Project Methodology • Departmental wide training on methodology • Enterprise Communications/Sessions • Job Class Specifications • Added Project Management Skill Set • Developed PM “Expert” Class • Hire top down – 4 to 6 month cycle
Pick One TQM CMM CMMI Six Sigma ITIL Etc…
Initial Assessment • Hired vendor to lead CMMI Level 3 assessment • Selected 3 major projects to review • Assembled dedicated team to participate • Provided training for team members • Completed data collection exercise • Produced final report / “as is” baseline
Mindset “A good plan violently executed today, is better than a perfect plan tomorrow” - George S. Patton
Plan of Attack • Two year implementation plan • Configuration Management • Project Panning • Project Monitoring & Control • Metrics & Analysis • Requirements Management • Supplier Management • Q.A. Process & Product • Involvement of all levels in effort • Incorporate into daily work efforts • Identify tools to assist (MS Project, Rational, Mercury, etc.)
Lessons Learned • Evaluate Capability of Organization • Set Strategic Goal Direction • Communications to all levels (Horizontal and Vertical) • Incorporate into Performance Plans • Funding is difficult • Seamless integration into normal work efforts • Track successes and communicate • Start process on new projects • Develop a “marketing” plan • Move quickly – “retirement bubble” is here
Background Slides
Project Management Process Main Steps TG2 TG1 TG3 TG4 Requirements Design Development Testing Deployment Deliverables • MCG Project Team Identified • Business Case • Cost/Benefit Analysis • Stakeholder Analysis • Requirements Definition Document (RDD) • Initial Schedule Estimate • Where required: • Procurement Plan • RFP • Contract • Risk Assessment and Risk Management Plan • System Design • Database Design • Security Plan / Design • Network Plan / Considerations • Initial Test Plan • Peer review of design and test plan • Detailed Project Management Plan and Schedule • Code and System Testing Complete • Training Plan • User Acceptance Testing Plan • Documentation Complete • Peer review of code, test plan and documentation • Adjustments to Schedule Identified (if any) • User Acceptance Testing Complete • Transition / Support Plan • Deployment / Installation / Reversion Plan • Security Review • Communication Plan • Conduct User Training • Monitoring and Support Tools Implemented • Peer review of deployment procedures • Adjustments to Schedule Identified (if any) • Where required: • Pilot phase and plan • System deployed in production • Post-Mortem Review of Project to Identify Best Practices and Lessons Learned