Software Process Improvement SPI Why Is Process Improvement
- Slides: 9
Software Process Improvement ��������� SPI
Why Is Process Improvement So Hard? • Challenge #1: Not Enough Time Challenge #2: Lack of Knowledge Challenge #3: Wrong Motivations Challenge #4: Dogmatic Approaches Challenge #5: Insufficient Commitment • What Should You Do?
An Effective Process Improvement Approach • The Process Improvement Cycle Focus on the Pain Communicate, Communicate Organize for Process Improvement Plan Your Actions Steer to Success
Personal Process Improvement • Project Planning and Tracking Requirements Design and Coding Quality Practices Maintenance
Process Improvement Traps to Avoid (1) • Trap #1: Lack of Management Commitment Trap #2: Unrealistic Management Expectations Trap #3: Time-Stingy Project Managers Trap #4: Stalling on Action Plan Implementation Trap #5: Achieving a Maturity Level Becomes the Primary Goal
Process Improvement Traps to Avoid (2) • Trap #6: Participants Are Inadequately Trained Trap #7: Expecting Defined Procedures to Make People Interchangeable Trap #8: Failing to Scale Processes to Project Size Trap #9: Process Improvement Becomes a Game Trap #10: Process Assessments are Ineffective
Creating a Process Assets Library • Motivation and Philosophy Best Practices or Good Practices? Our Approach Good Practices Content Web Site Architecture
Molding the CMM to Your Organization • Why Not Just "Do the CMM"? Process Assessment Molding the CMM Tracking Progress
A Modular Mini-Assessment Method • Background Method Description Supporting Infrastructure Experience Report
