Description
Business process improvement (BPI) is a systematic approach to help an organization optimize its underlying processes to achieve more efficient results.
Process Improvement Plan
Doc ID: Date: Revision: Status:
Abstract
This document describes the process improvement plan for Company XXX.
For Internal Use Only © Centre for Software Engineering
Process Improvement Plan
Approvals
Approvals. Author
Signed.
Date.
For Internal Use Only Page 2 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
Revision History
Revision Release Date
1.0
Author
Reason for Change
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 3 of 19
Process Improvement Plan
Table of Contents
APPROVALS .......................................................................................................2 REVISION HISTORY............................................................................................3 TABLE OF CONTENTS .......................................................................................4 1 INTRODUCTION ...........................................................................................5 1.1 1.2 1.3 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 4 4.1 4.2 4.3 PURPOSE OF THE DOCUMENT ....................................................................5 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS...........................................5 REFERENCES............................................................................................5 PROJECT OVERVIEW .................................................................................6 PROJECT SCOPE.......................................................................................6 PROJECT GOALS .......................................................................................6 PROJECT OBJECTIVES ...............................................................................7 KEY STAKEHOLDERS .................................................................................7 PROJECT RESOURCES...............................................................................8 CRITICAL SUCCESS FACTORS ....................................................................8 CRITICAL ASSUMPTIONS ............................................................................9 CRITICAL CONSTRAINTS ............................................................................9 CRITICAL DEPENDENCIES ........................................................................10 RISK MANAGEMENT .................................................................................11 ISSUE MANAGEMENT ...............................................................................11 PROJECT TRACKING ................................................................................11 PROJECT STATUS REPORTING .................................................................11 MANAGEMENT REVIEW ............................................................................12 IMPLEMENTATION MANAGEMENT ..............................................................13 CONFIGURATION MANAGEMENT................................................................13 TRAINING REQUIREMENTS .......................................................................13 PROJECT DELIVERABLES .........................................................................13 WORK BREAK DOWN STRUCTURE ............................................................15 PROJECT SCHEDULE ...............................................................................15 KEY MILESTONES ....................................................................................16
PROJECT DESCRIPTION ............................................................................6
PROJECT MANAGEMENT.........................................................................11
PROJECT BREAKDOWN...........................................................................15
For Internal Use Only Page 4 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
1 Introduction 1.1 Purpose of the Document
The purpose of this document is to describe the Process Improvement Plan for XXX. Included is a description of the goals, activities and responsibilities for implementing this process improvement plan. It will describe how the project will be delivered and demonstrate the benefits that will be realised.
1.2
CMMI PI QA QAP
Definitions, Acronyms, and Abbreviations
Capability Maturity Model Integration Process Improvement Quality Assurance Quality Assurance Plan
1.3
References
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 5 of 19
Process Improvement Plan
2 Project Description 2.1 Project Overview
Process Improvement is a key area of advancement for XXX. This process improvement plan is a statement of all PI initiatives and should be used as a guide for the organisation. The PI goals are in direct support of the business goals and initiatives.
2.2
2.2.1
Project Scope
In-Scope
Identify the scope of the project. Which areas, groups, and or projects within your company will be included in your process improvement initiative?
2.2.2
Out-of-Scope
Identify what is not included for this improvement initative.
2.3
Goal 1
Project Goals
Identify the goals of the project:
Goal 2
Goal 3
For Internal Use Only Page 6 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
2.4
Project Objectives
Identify the objectives of the project. Objective 1 •
Objective 2 •
Objective 3 •
2.5
Key Stakeholders
The stakeholders for the process improvement project are as follows: Role Representative Responsibility
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 7 of 19
Process Improvement Plan
2.6
Project Resources
To support the implementation of this process improvement plan the following resources will be required to be available as needed. Role Sponsor Process Champion Representative Responsibility Provide direction and support. Act as Project Manager for the process improvement project, provide leadership and promote process improvement within the organisation To provide assistance & expertise throughout the process improvement project
Steering Group
2.7
Critical Success Factors
Critical Success Factor
The following are the critical success factors for the project. Reference CSF1 CSF2 CSF3 CSF4
For Internal Use Only Page 8 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
2.8
Assumptions
The following are the known assumptions, which have been identified for the project at the date of publishing the current version of the ‘Project Plan’. It is possible that other assumptions will be made as the Project progresses and if so they will be covered in future releases of this document. Reference A1 A2 A3 A4 Assumption
2.9
Constraints
The following are the known constraints, which have been identified for the project at the date of publishing the current version of the ‘Project Plan’. It is possible that other constraints will emerge as the Project progresses and if so they will be covered in future releases of this document. Reference C1 C2 C3 C4 Constraint
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 9 of 19
Process Improvement Plan
2.10
Dependencies
The following are the dependencies, which have been identified for the project at the date of publishing the current version of the ‘Project Plan’. It is possible that other dependencies will emerge as the Project progresses and if so they will be covered in future releases of this document. Reference D1 D2 D3 D4 Dependency
For Internal Use Only Page 10 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
3 Project Management 3.1 Risk Management
A Project risk is any event that may occur that can have a negative impact on the
Project. The approach to ‘Risk Management’ on this Project will be to identify risks as early as possible, take remedial action necessary to remove or reduce the risk to an acceptable level. The Process Champions will be responsible for identifying, quantifying and reporting on risks during the Project. The risks associated with this project have been identified and logged in the Project Risk Table shown in Appendix A.
3.2
Issue Management
As the Project progress issues will be identified and raised by Project Participants. These issues will require some ‘Action’ or ‘Decision’ to be taken. All issues for the project will be logged in the Issue Log shown in Appendix B.
3.3
Project Tracking
Regular project meetings to discuss issues and progress will be held with all process improvement participants and management in attendance. In addition the overall project status will be reviewed with the CSE Mentor on a monthly basis. The project schedule and risks will be tracked and updated weekly.
3.4
Project Status Reporting
The overall project progress will be reviewed XXXX (daily/weekly/fortnightly) and a status report will be produced for the project on a XXXX basis. The project status will be reported using the RAG (Red, Amber and Green) method. The current status is project status in the reporting period, while the Prognosis RAG Status will be the ultimate end result with Risk, Issue, Change Requests, Project dependencies and other mitigating actions taken into consideration.
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 11 of 19
Process Improvement Plan
The following criteria will be used to determine the Current RAG Status.
Current Status Criteria
Green
All Project components are ‘On-Target’ when compared against plan
Amber
If more than 1/3 of the Project components are considered 15% or more behind expectations
Red
If more than 1/2 of the Project components are considered 15% or more behind expectations
Prognosis Status Criteria
Green
No new or existing Issues, Risks, Changes or Project Dependencies that are likely to adversely affect the planned delivery date of the Project.
Amber
New or existing Issues, Risks, Changes or Project Dependencies are likely to adversely affect the planned delivery date of the Project.
Red
Any Issue, Risk, Change or Dependency that will cause a “threat” to the Project being able to deliver on time and to cost.
3.5
Management Review
Status reports will be sent to management on a weekly basis. In addition Management Project Reviews will take place on a periodic basis. These have been scheduled on the Project Schedule in Appendix C.
For Internal Use Only Page 12 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
3.6
Implementation Management
An implementation plan will be produced to address how improvements will be introduced into the organisation. The activities associated with documenting the implementation plan will be included on the project schedule.
3.7
Configuration Management
All work products produced by this project will be placed under Configuration Management.
3.8
Training Requirements
Identify the training requirements for the project.
3.9
Project Deliverables
The following is a list of Project deliverables identified at the date of publishing current version of the ‘Project Plan’. It is possible that other deliverables will be identified during the course of the Project and these will be included in future releases of this document. Deliverable Process Improvement Plan Project Schedule Project Risk Log Project Issue Log Status Reports Implementation Plan Responsibility Process Champion Process Champion Process Champion Process Champion Process Champion Process Champion Project Stage Project Initiation Project Initiation Project Initiation Project Initiation Throughout project the
Implementation Phase
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 13 of 19
Process Improvement Plan
3.10
Project Repository
Identify the location of all project deliverables. It will be the responsibility of the process champion to maintain the project repository.
For Internal Use Only Page 14 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
4 Project Breakdown 4.1 Work Breakdown Structure
The following are the high level tasks to be carried out for the project and the estimated effort required for each task. Task Id Task Description Estimated Effort (Hrs)
4.2
Project Schedule
The project schedule is shown in Appendix B. The project schedule will be closely tracked and reported throughout the lifecycle of the project. This will enable planned action to be taken as soon as possible so that the project can be kept in control. The Project Schedule in Appendix C will be used to track the schedule on a XXXX basis.
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 15 of 19
Process Improvement Plan
4.3
Key Milestones
The key project milestones are as follows:
Milestone
Date
For Internal Use Only Page 16 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
Appendix A
Project Risk Log
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 17 of 19
Process Improvement Plan
Appendix B
Project Issue Log
For Internal Use Only Page 18 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
Appendix C
Project Schedule
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 19 of 19
doc_278799061.pdf
Business process improvement (BPI) is a systematic approach to help an organization optimize its underlying processes to achieve more efficient results.
Process Improvement Plan
Doc ID: Date: Revision: Status:
Abstract
This document describes the process improvement plan for Company XXX.
For Internal Use Only © Centre for Software Engineering
Process Improvement Plan
Approvals
Approvals. Author
Signed.
Date.
For Internal Use Only Page 2 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
Revision History
Revision Release Date
1.0
Author
Reason for Change
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 3 of 19
Process Improvement Plan
Table of Contents
APPROVALS .......................................................................................................2 REVISION HISTORY............................................................................................3 TABLE OF CONTENTS .......................................................................................4 1 INTRODUCTION ...........................................................................................5 1.1 1.2 1.3 2 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 2.10 3 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 4 4.1 4.2 4.3 PURPOSE OF THE DOCUMENT ....................................................................5 DEFINITIONS, ACRONYMS, AND ABBREVIATIONS...........................................5 REFERENCES............................................................................................5 PROJECT OVERVIEW .................................................................................6 PROJECT SCOPE.......................................................................................6 PROJECT GOALS .......................................................................................6 PROJECT OBJECTIVES ...............................................................................7 KEY STAKEHOLDERS .................................................................................7 PROJECT RESOURCES...............................................................................8 CRITICAL SUCCESS FACTORS ....................................................................8 CRITICAL ASSUMPTIONS ............................................................................9 CRITICAL CONSTRAINTS ............................................................................9 CRITICAL DEPENDENCIES ........................................................................10 RISK MANAGEMENT .................................................................................11 ISSUE MANAGEMENT ...............................................................................11 PROJECT TRACKING ................................................................................11 PROJECT STATUS REPORTING .................................................................11 MANAGEMENT REVIEW ............................................................................12 IMPLEMENTATION MANAGEMENT ..............................................................13 CONFIGURATION MANAGEMENT................................................................13 TRAINING REQUIREMENTS .......................................................................13 PROJECT DELIVERABLES .........................................................................13 WORK BREAK DOWN STRUCTURE ............................................................15 PROJECT SCHEDULE ...............................................................................15 KEY MILESTONES ....................................................................................16
PROJECT DESCRIPTION ............................................................................6
PROJECT MANAGEMENT.........................................................................11
PROJECT BREAKDOWN...........................................................................15
For Internal Use Only Page 4 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
1 Introduction 1.1 Purpose of the Document
The purpose of this document is to describe the Process Improvement Plan for XXX. Included is a description of the goals, activities and responsibilities for implementing this process improvement plan. It will describe how the project will be delivered and demonstrate the benefits that will be realised.
1.2
CMMI PI QA QAP
Definitions, Acronyms, and Abbreviations
Capability Maturity Model Integration Process Improvement Quality Assurance Quality Assurance Plan
1.3
References
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 5 of 19
Process Improvement Plan
2 Project Description 2.1 Project Overview
Process Improvement is a key area of advancement for XXX. This process improvement plan is a statement of all PI initiatives and should be used as a guide for the organisation. The PI goals are in direct support of the business goals and initiatives.
2.2
2.2.1
Project Scope
In-Scope
Identify the scope of the project. Which areas, groups, and or projects within your company will be included in your process improvement initiative?
2.2.2
Out-of-Scope
Identify what is not included for this improvement initative.
2.3
Goal 1
Project Goals
Identify the goals of the project:
Goal 2
Goal 3
For Internal Use Only Page 6 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
2.4
Project Objectives
Identify the objectives of the project. Objective 1 •
Objective 2 •
Objective 3 •
2.5
Key Stakeholders
The stakeholders for the process improvement project are as follows: Role Representative Responsibility
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 7 of 19
Process Improvement Plan
2.6
Project Resources
To support the implementation of this process improvement plan the following resources will be required to be available as needed. Role Sponsor Process Champion Representative Responsibility Provide direction and support. Act as Project Manager for the process improvement project, provide leadership and promote process improvement within the organisation To provide assistance & expertise throughout the process improvement project
Steering Group
2.7
Critical Success Factors
Critical Success Factor
The following are the critical success factors for the project. Reference CSF1 CSF2 CSF3 CSF4
For Internal Use Only Page 8 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
2.8
Assumptions
The following are the known assumptions, which have been identified for the project at the date of publishing the current version of the ‘Project Plan’. It is possible that other assumptions will be made as the Project progresses and if so they will be covered in future releases of this document. Reference A1 A2 A3 A4 Assumption
2.9
Constraints
The following are the known constraints, which have been identified for the project at the date of publishing the current version of the ‘Project Plan’. It is possible that other constraints will emerge as the Project progresses and if so they will be covered in future releases of this document. Reference C1 C2 C3 C4 Constraint
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 9 of 19
Process Improvement Plan
2.10
Dependencies
The following are the dependencies, which have been identified for the project at the date of publishing the current version of the ‘Project Plan’. It is possible that other dependencies will emerge as the Project progresses and if so they will be covered in future releases of this document. Reference D1 D2 D3 D4 Dependency
For Internal Use Only Page 10 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
3 Project Management 3.1 Risk Management
A Project risk is any event that may occur that can have a negative impact on the
Project. The approach to ‘Risk Management’ on this Project will be to identify risks as early as possible, take remedial action necessary to remove or reduce the risk to an acceptable level. The Process Champions will be responsible for identifying, quantifying and reporting on risks during the Project. The risks associated with this project have been identified and logged in the Project Risk Table shown in Appendix A.
3.2
Issue Management
As the Project progress issues will be identified and raised by Project Participants. These issues will require some ‘Action’ or ‘Decision’ to be taken. All issues for the project will be logged in the Issue Log shown in Appendix B.
3.3
Project Tracking
Regular project meetings to discuss issues and progress will be held with all process improvement participants and management in attendance. In addition the overall project status will be reviewed with the CSE Mentor on a monthly basis. The project schedule and risks will be tracked and updated weekly.
3.4
Project Status Reporting
The overall project progress will be reviewed XXXX (daily/weekly/fortnightly) and a status report will be produced for the project on a XXXX basis. The project status will be reported using the RAG (Red, Amber and Green) method. The current status is project status in the reporting period, while the Prognosis RAG Status will be the ultimate end result with Risk, Issue, Change Requests, Project dependencies and other mitigating actions taken into consideration.
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 11 of 19
Process Improvement Plan
The following criteria will be used to determine the Current RAG Status.
Current Status Criteria
Green
All Project components are ‘On-Target’ when compared against plan
Amber
If more than 1/3 of the Project components are considered 15% or more behind expectations
Red
If more than 1/2 of the Project components are considered 15% or more behind expectations
Prognosis Status Criteria
Green
No new or existing Issues, Risks, Changes or Project Dependencies that are likely to adversely affect the planned delivery date of the Project.
Amber
New or existing Issues, Risks, Changes or Project Dependencies are likely to adversely affect the planned delivery date of the Project.
Red
Any Issue, Risk, Change or Dependency that will cause a “threat” to the Project being able to deliver on time and to cost.
3.5
Management Review
Status reports will be sent to management on a weekly basis. In addition Management Project Reviews will take place on a periodic basis. These have been scheduled on the Project Schedule in Appendix C.
For Internal Use Only Page 12 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
3.6
Implementation Management
An implementation plan will be produced to address how improvements will be introduced into the organisation. The activities associated with documenting the implementation plan will be included on the project schedule.
3.7
Configuration Management
All work products produced by this project will be placed under Configuration Management.
3.8
Training Requirements
Identify the training requirements for the project.
3.9
Project Deliverables
The following is a list of Project deliverables identified at the date of publishing current version of the ‘Project Plan’. It is possible that other deliverables will be identified during the course of the Project and these will be included in future releases of this document. Deliverable Process Improvement Plan Project Schedule Project Risk Log Project Issue Log Status Reports Implementation Plan Responsibility Process Champion Process Champion Process Champion Process Champion Process Champion Process Champion Project Stage Project Initiation Project Initiation Project Initiation Project Initiation Throughout project the
Implementation Phase
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 13 of 19
Process Improvement Plan
3.10
Project Repository
Identify the location of all project deliverables. It will be the responsibility of the process champion to maintain the project repository.
For Internal Use Only Page 14 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
4 Project Breakdown 4.1 Work Breakdown Structure
The following are the high level tasks to be carried out for the project and the estimated effort required for each task. Task Id Task Description Estimated Effort (Hrs)
4.2
Project Schedule
The project schedule is shown in Appendix B. The project schedule will be closely tracked and reported throughout the lifecycle of the project. This will enable planned action to be taken as soon as possible so that the project can be kept in control. The Project Schedule in Appendix C will be used to track the schedule on a XXXX basis.
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 15 of 19
Process Improvement Plan
4.3
Key Milestones
The key project milestones are as follows:
Milestone
Date
For Internal Use Only Page 16 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
Appendix A
Project Risk Log
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 17 of 19
Process Improvement Plan
Appendix B
Project Issue Log
For Internal Use Only Page 18 of 19 Sample Process Improvement Plan.doc © Centre for Software Engineering 5/8/2009 Revision 1.0
Process Improvement Plan
Appendix C
Project Schedule
For Internal Use Only 5/8/2009 Revision 1.0 Sample Process Improvement Plan.doc © Centre for Software Engineering Page 19 of 19
doc_278799061.pdf