Software process maturity

1
CFICSE 2000
Software process maturity SP-02 Lt(N) Claude
Bernard
2
References

• Managing the Software Process, Watts S. Humphrey,
  Addison-Wesley, ISBN 0-201-18095-2
• A discipline for software engineering, Watts S.
  Humphrey, Addison-Wesley, ISBN 0-201-54610-8

3
Software Process

• Software process is the collection of tools,
  methods and practices, that we use to make a
  software product and
• To predict our performance
• It can be controlled, measured and improved
• It aim for a balanced between creativity and
  repeatability

4
Software Process Improvement

• Six steps to improve software capabilities
• 1. Understand the current development process or
  processes
• 2. Develop a vision of the desired process
• 3. List the required process improvement actions
  in order of priority
• 4. Produce a plan to implement the actions
• 5. Commit the resources to execute the plan
• 6. Start over at step 1

5
Capability maturity model (CMM)

• used as a standard for appraising the current
  state of the organizations software process and
  as a guide for identifying and prioritizing the
  actions comprising the software process
  improvement effort.
• Made up of 5 levels and 18 key process areas (KPA)

6
Process Maturity Levels
Optimizing
Process Control
Managed
Process Measurement
Defined
Process Definition
Repeatable
Basic Management Control
Initial
7
The initial process

• (A.K.A. total chaos)
• No management mechanism in place to plan and
  track the work of individuals
• If procedures are established they are abandoned
  during a crisis (Which tends to be continuous)

8
To improve to repeatable process

• Learn between speed and progress
• Basic project control
• Project management
• Management oversight
• Quality assurance
• Change control

9
The repeatable process

• Provides control over the way the organization
  establishes its plan and commitments
• Experienced at doing similar work

10
Repeateable - KPA

• Software configuration management
• Software quality assurance
• Software subcontract management
• Software project tracking and oversight
• Software project planning
• Requirements management

11
To improve to the defined process

• Establish a process group
• Establish a development process architecture
• Introduce a family of software engineering
  methods and technologies

12
The defined process

• When faced with a crisis they will continue to
  use the process that has been defined
• Little data to support the effectiveness of the
  process
• Not clear what can or should be measured

13
Defined - KPA

• Peer reviews
• Intergroup coordination
• Software product engineering
• Integrated software management
• Training program
• Software process definition
• Software process focus

14
Area of greatest risk

• Organization faces major risks
• New tools will affect the process
• Entering new territory, by trying new product
• Major organizational changes can be very
  disruptive

15
To improve to the managed process

• Establish basic process measurements to identify
  quality and cost of each process step
• Establish database and resource to maintain it
  (gathering of data)
• Provide sufficient resource with proper skill
• Assess the quality of the process and report to
  management

16
The managed process

• High cost of gathering data
• Definition of the measured data
• Process data must not be used to compare projects
  or individuals

17
Managed KPA

• Quality management
• quantitative process management

18
To improve to the optimizing process

• Automatic gathering of process data
• Use process data to analyze and modify the process

19
The optimizing process

• The data is available to tune the process itself
• Ability to put the resources where it counts

20
Optimizing KPA

• Process change management
• Technology change management
• Defect prevention

21
The people in the process

• There are never enough good people
• Awareness of the process leads to better
  communication
• Provides a disciplined environment for
  professional work

22
The need for the optimizing process

• Increasingly sensitive application
• More demanding users
• Increased risk of errors
• It is less expensive to build good quality
  software the first time, than to try to fix
  numerous errors on subsequent revision.