IDC PeerScape: Practices to Adopt Mainframe DevOps
This IDC PeerScape describes five practices that organizations should consider when planning to adopt mainframe DevOps gleaned from conversations with three organizations: Nedbank, a South African bank; a European financial market infrastructure (FMI) provider; and a Canadian financial services company."The desired state of enterprise DevOps is one where mainframe systems are viewed as just another platform, and the people, processes, and tools that go into application development are unified and coordinated," said Katie Norton, senior research analyst, DevOps and DevSecOps at IDC. "There is not a blueprint for adopting mainframe DevOps, so organizations can benefit from the lessons learned by those that are further along in their journey."
Please Note: Extended description available upon request.
- IDC PeerScape Figure
- Executive Summary
- Peer Insights
- Practice 1: Architect a Toolchain That Balances Standardization with Flexibility
- Challenge
- Example
- Guidance
- Practice 2: Note That Cultural Change Should Be Incremental and Leader Led
- Challenge
- Example
- Guidance
- Practice 3: Migrate to Git Incrementally
- Challenge
- Example
- Guidance
- Practice 4: Cultivate Next-Gen Mainframe Talent
- Challenge
- Example
- Guidance
- Practice 5: Track Key DevOps Research and Assessment Metrics to Measure Success
- Challenge
- Example
- Guidance
Research Assistance
Download our eBook: How to Succeed Using Market Research
Learn how to effectively navigate the market research process to help guide your organization on the journey to success.
Download eBook