IISP International Institute for Software ProcessCertified Software Process Improvement Professional Certification (CSPIP) Company


This tutorial covers CKA area #5 of the International Software Process Improvement Certification (ISPIC) requirements.

Planning a software process improvement project is only the beginning for demonstrating the full impact that will help the company adapt to today’s competitive environment.  Success depends on implementing the new process successfully and achieving the value the effort promised. Learn the approaches you need to pilot the new mission critical process and streamline it. Use GSEPs (Good Software Engineering Processes) that have a track record of success to guide the pilot and the full roll out to get optimized improvement outcomes.

Participant will learn to:

  • Sustain senior management support by demonstrating SPI results
  • Demonstrate SPI impact through successful piloting process
  • Institutionalize improved process through integrating lessons learned from pilot and executing a smooth roll out plan
  • Demonstrate improved productivity and quality through management-oriented metrics
  • Change the culture based on engaging stakeholders during the pilot and roll out and establishing process management and operational integration

Core Knowledge Area Requirements:

  • Organizational change management
  • Pilot testing and rolling out process changes in organizations
  • Training people to adopt new processes
  • Communicating and gaining support for changes involved with the software process improvement process as well as for specific software process improvements and their associated improvement projects
  • Institutionalizing continuous software process improvement attitudes and behaviors in the organization
  • Evaluating effectiveness of software process change
  • Dealing with cultural, Organization and People issues concerning software process change.

  1. Context for Implementing SPI Projects
    1. Understanding processes
    2. Defining the chain of processes
    3. Where SPI fits in the organization
    4. Where implementation fits into the SPI process
  2. Culture Change
    1. Understanding what culture change is and how to manage it
      1. Culture clash and prognosis
    2. Planning culture change
      1. Analyzing culture
      2. Analyzing impact and risk
      3. Plan pilot and roll out culture change
      4. SWOT analysis
      5. Creating strategic and tactical plans
      6. Applying Project management tools to SPI implementation
  3. Implementation
    1. Implementation process steps
    2. Plan-Do-Check-Act applied to implementation
    3. Roles and responsibilities
  4. Keeping management and pilot team support
    1. Demonstrating value
    2. Partnership model
    3. Communication planning; analyzing complexity
    4. Communication effectiveness models
  5. Culture change strategies
    1. Aligned assertive communication model
    2. Consensus building
    3. Influence strategies to get buy in from all pilot and roll out stakeholders
    4. Creating training plan
    5. Pilot
    6. Roll out
  6. Evaluate effectiveness
    1. Measure new mission critical process effectiveness, efficiency
  7. Useful tools
  8. Putting it all together to build an SPI program

Rebecca Staton-Reinstein, Ph.D., CSQA, president of Advantage Leadership, works with you to improve bottom- and top-line results. In a recent engagement her client realized over $6 million in savings on an SPI project and the results are still adding up. Doctor Rebecca clients span the globe, represent all economic sectors, and share a desire to become more effective and efficient through continuous improvement with greater employee engagement, customer delight, and marketplace success. She is the author of several books and was elected to the St. Petersburg Engineering Academy for her work on SPI in Russia.

©2010 International Institute for Software Process