ALM and ITIL: spanning the divide with IT operations
Runtime has long been the neglected half of the application lifecycle, a phase when development organizations typically hand off responsibilities to IT operations (ITO). With both sides torn by entrenched cultural divides, problem resolution inevitably degenerates to finger-pointing and, ultimately, added costs. Because “dev-ops” collaborations are rare, it reinforces the notion that IT is incapable of delivering quality products that bring value to the business when the business needs them.
Both sides have developed their own process disciplines. Numerous software development lifecycle (SDLC) methodologies have emerged. However, with growing acceptance of the ITIL framework (especially in regions such as Western Europe and across larger organizations), IT service management (ITSM) professionals have seized the initiative in asserting process discipline to improve IT-to-business integration, ITO efficiency, and the quality of IT service delivery.
Both sides have developed their own process disciplines. Numerous software development lifecycle (SDLC) methodologies have emerged. However, with growing acceptance of the ITIL framework (especially in regions such as Western Europe and across larger organizations), IT service management (ITSM) professionals have seized the initiative in asserting process discipline to improve IT-to-business integration, ITO efficiency, and the quality of IT service delivery.
SUMMARY
Impact
Ovum view
Key messages
GETTING BEYOND FINGER-POINTING
The problem: production is the missing link in the application lifecycle
There is a better way
RECAP: THE DEVELOPMENT SOLUTION TO “DEV-OPS” COLLABORATION
Adopt a design-for-manufacturing approach
Treat software as a durable good
ITIL provides a logical context for “dev-ops” interaction
Inception
Construction
Transition
Operation and continuous improvement
SOLUTION FROM THE ITO SIDE: APPLY ITIL TO CROSS THE DIVIDE
Adopt a federated approach to lifecycle management
Not just an arbitrary connecting of the dots
Using RACI to map out the roles
Focus on key ITIL processes
Incident management
Problem management
Change management
Configuration management
Release management
Service-level management
RECOMMENDATIONS
Recommendations for enterprises
Recommendations for ITSM tools vendors
APPENDIX
Further reading
Methodology
Impact
Ovum view
Key messages
GETTING BEYOND FINGER-POINTING
The problem: production is the missing link in the application lifecycle
There is a better way
RECAP: THE DEVELOPMENT SOLUTION TO “DEV-OPS” COLLABORATION
Adopt a design-for-manufacturing approach
Treat software as a durable good
ITIL provides a logical context for “dev-ops” interaction
Inception
Construction
Transition
Operation and continuous improvement
SOLUTION FROM THE ITO SIDE: APPLY ITIL TO CROSS THE DIVIDE
Adopt a federated approach to lifecycle management
Not just an arbitrary connecting of the dots
Using RACI to map out the roles
Focus on key ITIL processes
Incident management
Problem management
Change management
Configuration management
Release management
Service-level management
RECOMMENDATIONS
Recommendations for enterprises
Recommendations for ITSM tools vendors
APPENDIX
Further reading
Methodology
LIST OF TABLES
Table 1: The RACI matrix
Table 1: The RACI matrix
LIST OF FIGURES
Figure 1: Mapping the application lifecycle to ITIL V3
Figure 2: Coordinating IT service planning with Agile software development
Figure 3: The impact of a high-software usage issue on the application lifecycle
Figure 4: ALM mapped to ITIL configuration management process
Figure 5: Different paths to IT portfolio management
Figure 1: Mapping the application lifecycle to ITIL V3
Figure 2: Coordinating IT service planning with Agile software development
Figure 3: The impact of a high-software usage issue on the application lifecycle
Figure 4: ALM mapped to ITIL configuration management process
Figure 5: Different paths to IT portfolio management