• Skip to main content
  • Skip to primary sidebar
  • Skip to secondary sidebar
  • Skip to footer

Computer Notes

Library
    • Computer Fundamental
    • Computer Memory
    • DBMS Tutorial
    • Operating System
    • Computer Networking
    • C Programming
    • C++ Programming
    • Java Programming
    • C# Programming
    • SQL Tutorial
    • Management Tutorial
    • Computer Graphics
    • Compiler Design
    • Style Sheet
    • JavaScript Tutorial
    • Html Tutorial
    • Wordpress Tutorial
    • Python Tutorial
    • PHP Tutorial
    • JSP Tutorial
    • AngularJS Tutorial
    • Data Structures
    • E Commerce Tutorial
    • Visual Basic
    • Structs2 Tutorial
    • Digital Electronics
    • Internet Terms
    • Servlet Tutorial
    • Software Engineering
    • Interviews Questions
    • Basic Terms
    • Troubleshooting
Menu

Header Right

Home » Software Engineering » Process Change Management (PCM)
Next →
← Prev

Process Change Management (PCM)

By Dinesh Thakur

Changes in the process are unavoidable and should be made to improve the productivity and quality of the process. These changes can be applied by using Process Change Management (PCM), which is a technique to improve the software processes in the organization. Thus, this technique helps in increasing productivity and quality by improving software processes for the developing software.

Process change management determines the process improvement goals, identifies, evaluates and implements improvements to the standard software process in the organization and defines software processes for the new projects to be developed. The organization follows a written policy for implementing software process improvements. The policy follows the steps listed below.

1. The organization has the quantitative and measurable goals to improve the software processes and tracks performance against these goals.

2. The organization’s process improvement is directed towards improving the quality, increasing productivity and decreasing the time for the development of the product.

3. The organization’s staff members participate in the process improvement.

Process improvement does not take place in a single stage; it is a continuous process which goes through different stages as listed in Table. The software process improvement activities are managed according to a documented procedure, which is maintained in the central repository. Review of the processes is conducted in a phased and structured manner to ensure that continuous process improvement activities are conducted and monitored.

                                           Table Process Improvement Stages

Stages

Description

Process analysis

Model and analyze existing processes.

Improvement identification

Identify quality, cost or schedule bottlenecks.

Process change introduction

Modify the process to remove identified bottlenecks.

Measure improvement

Compare outputs between previous and changed processes.

Process change training

Train staff involved in new process proposals.

Change tuning

Evolve and improve process improvements.

Training programs are established to enable and encourage individuals in the organization to participate in the process improvement activities. Improvement opportunities are identified and evaluated, which benefit the organization. When software process improvements are approved for general practice, the organization standard software process and the project-defined software processes are revised appropriately.

Software process change management follows a procedure for improving the software processes in the organization. This procedure specifies the following steps.

1. The improvement of the software process requires a proposal to be submitted, which includes the organization’s software process improvement goals and recommendations for software process assessment. In addition, it contains analysis of data on the performance of the project as compared to the quality of the software and the productivity goals.

2. The proposal is evaluated to ensure whether to implement it. The decision for implementing the proposal is then documented.

3. The benefits expected from the software process are determined. These benefits include quality of the product, end user satisfaction, and so on.

4. The priority of software process improvement proposals is determined, according to which selection for the implementation is made.

5. Implementation of the software process improvement actions resulting from the proposal is assigned and planned.

6. The actions for software process improvement, which require significant effort, are assigned to the team responsible for implementing the actions.

7. The status of each process improvement proposal is monitored.

8. Software process improvement proposals whose responses are unusually long are identified and acted upon.

9. The user reviews the changes before they are implemented, which are estimated to have an impact on the quality of the product.

10. When the actions of the software process improvement are completed, they are reviewed and verified.

11. The submitter of the software process improvement proposal receives acknowledgement of proposals and notification of the disposition. of the proposals.

When a decision is made to transfer software process improvement into general practice, the improvement is again implemented according to a documented procedure, which specifies the following steps.

1. The resources required to manage the changes in the software process are established.

2. The strategy to collect data for evaluating and monitoring changes in the performance of the software process is reviewed, agreed and documented. The individuals, who are implementing the software processes affected by the change, agree to this strategy. The support tools are instrumented accordingly to record the required data automatically.

3. Training is provided before installing the process change for general use. Training courses are updated to reflect the current software processes.

4. Appropriate process changes are incorporated into the organization’s standard software process and the project-defined software processes.

You’ll also like:

  1. Technology Change Management (TCM)
  2. Explain Various Phases of Process Management
  3. Quantitative Process Management (QPM)
  4. Explain Software Configuration Management Process
  5. Requirements Management Process in Software Engineering
Next →
← Prev
Like/Subscribe us for latest updates     

About Dinesh Thakur
Dinesh ThakurDinesh Thakur holds an B.C.A, MCDBA, MCSD certifications. Dinesh authors the hugely popular Computer Notes blog. Where he writes how-to guides around Computer fundamental , computer software, Computer programming, and web apps.

Dinesh Thakur is a Freelance Writer who helps different clients from all over the globe. Dinesh has written over 500+ blogs, 30+ eBooks, and 10000+ Posts for all types of clients.


For any type of query or something that you think is missing, please feel free to Contact us.


Primary Sidebar

Software Engineering

Software Engineering

  • SE - Home
  • SE - Feasibility Study
  • SE - Software
  • SE - Software Maintenance Types
  • SE - Software Design Principles
  • SE - Prototyping Model
  • SE - SRS Characteristics
  • SE - Project Planning
  • SE - SRS Structure
  • SE - Software Myths
  • SE - Software Requirement
  • SE - Architectural Design
  • SE - Software Metrics
  • SE - Object-Oriented Testing
  • SE - Software Crisis
  • SE - SRS Components
  • SE - Layers
  • SE - Problems
  • SE - Requirements Analysis
  • SE - Software Process
  • SE - Software Metrics
  • SE - Debugging
  • SE - Formal Methods Model
  • SE - Management Process
  • SE - Data Design
  • SE - Testing Strategies
  • SE - Coupling and Cohesion
  • SE - hoc Model
  • SE - Challenges
  • SE - Process Vs Project
  • SE - Requirements Validation
  • SE - Component-Level Design
  • SE - Spiral Model
  • SE - RAD Model
  • SE - Coding Guidelines
  • SE - Techniques
  • SE - Software Testing
  • SE - Incremental Model
  • SE - Programming Practices
  • SE - Software Measurement
  • SE - Software Process Models
  • SE - Software Design Documentation
  • SE - Software Process Assessment
  • SE - Process Model
  • SE - Requirements Management Process
  • SE - Time Boxing Model
  • SE - Measuring Software Quality
  • SE - Top Down Vs Bottom UP Approaches
  • SE - Components Applications
  • SE - Error Vs Fault
  • SE - Monitoring a Project
  • SE - Software Quality Factors
  • SE - Phases
  • SE - Structural Testing
  • SE - COCOMO Model
  • SE - Code Verification Techniques
  • SE - Classical Life Cycle Model
  • SE - Design Techniques
  • SE - Software Maintenance Life Cycle
  • SE - Function Points
  • SE - Design Phase Objectives
  • SE - Software Maintenance
  • SE - V-Model
  • SE - Software Maintenance Models
  • SE - Object Oriented Metrics
  • SE - Software Design Reviews
  • SE - Structured Analysis
  • SE - Top-Down & Bottom up Techniques
  • SE - Software Development Phases
  • SE - Coding Methodology
  • SE - Emergence
  • SE - Test Case Design
  • SE - Coding Documentation
  • SE - Test Oracles
  • SE - Testing Levels
  • SE - Test Plan
  • SE - Staffing
  • SE - Functional Testing
  • SE - Bottom-Up Design
  • SE - Software Maintenance
  • SE - Software Design Phases
  • SE - Risk Management
  • SE - SRS Validation
  • SE - Test Case Specifications
  • SE - Software Testing Levels
  • SE - Maintenance Techniques
  • SE - Software Testing Tools
  • SE - Requirement Reviews
  • SE - Test Criteria
  • SE - Major Problems
  • SE - Quality Assurance Plans
  • SE - Different Verification Methods
  • SE - Exhaustive Testing
  • SE - Project Management Process
  • SE - Designing Software Metrics
  • SE - Static Analysis
  • SE - Software Project Manager
  • SE - Black Box Testing
  • SE - Errors Types
  • SE - Object Oriented Analysis

Other Links

  • Software Engineering - PDF Version

Footer

Basic Course

  • Computer Fundamental
  • Computer Networking
  • Operating System
  • Database System
  • Computer Graphics
  • Management System
  • Software Engineering
  • Digital Electronics
  • Electronic Commerce
  • Compiler Design
  • Troubleshooting

Programming

  • Java Programming
  • Structured Query (SQL)
  • C Programming
  • C++ Programming
  • Visual Basic
  • Data Structures
  • Struts 2
  • Java Servlet
  • C# Programming
  • Basic Terms
  • Interviews

World Wide Web

  • Internet
  • Java Script
  • HTML Language
  • Cascading Style Sheet
  • Java Server Pages
  • Wordpress
  • PHP
  • Python Tutorial
  • AngularJS
  • Troubleshooting

 About Us |  Contact Us |  FAQ

Dinesh Thakur is a Technology Columinist and founder of Computer Notes.

Copyright © 2025. All Rights Reserved.

APPLY FOR ONLINE JOB IN BIGGEST CRYPTO COMPANIES
APPLY NOW