Configuration Change

1
Configuration Change Release Management
Presented by Michael Mulvihill Stay
Technologies [phone] mulvihill3973_at_roger
s.com
2
Objectives of this Presentation

• To demonstrate the value-added potential of
  implementing a Configuration, Change Release
  (CCR) Management process
• To show how CCR Management integrate into the
  Project Management discipline
• To present a CCR Framework
• To demonstrate methods of showing results to
  inform stakeholders and stimulate continuous
  process improvement

3
What is CCR Management
Discipline for controlling the evolution of
software systems

• Enablers
• CCR Tools
• Policies and Procedures
• User Acceptance
• Learning from our mistakes
• Continual Improvement

• Objectives
• Do more with fewer resources
• Develop applications faster
• Improve quality of product
• Build systems that support the customer
• Explore new technology

Value is in the process
4
What are the Opportunities
Achieve productivity gains and ensure integrity
of the product. We can achieve this through
evolving the CCR Management Process.
SEIs Capability Maturity Model (CMM)

• Initial ad hoc, chaotic
• Repeatable disciplined process
• Defined standard, consistent process
• Managed predictable process
• Optimized continuous process improvement

Very significant increases in productivity can be
attained as we move up The Maturity Model
5
Long Term Goals

• Build in quality as software is developed rather
  than test for it afterwards
• Develop a learning organization for continual
  improvement
• Benefits can be measured and maximized

6
The Balanced Scorecard

• Vision
• Information Technology will provide knowledge,
  tools and processes needed to service its
  customers with innovative solutions
• Satisfy User expectations
• Business value of IT Infrastructure initiatives
  can be measured
• Goals
• Retain corporate memory
• Provide managers with the information needed to
  manage effectively and make informed decisions
• Deliver innovative and timely solutions and
  services
• Provide a stable, secure and reliable
  infrastructure that enables the business
• Produce results for continuous improvement

7
The Balanced Scorecard
8
(No Transcript)
9
(No Transcript)
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)
13
Showing Results
14
(No Transcript)
15
(No Transcript)
16
(No Transcript)
17
Lessons Learned

• Need a champion at a high level
• Quick successes
• Show performance reporting/measurement results
• 1 level of CMM at a time
• Prototype to get buy-in
• Need all pieces (configuration, change release)
• Cant attain perfection
• Need to instill Pride of Ownership