DevOps for the IBM Mainframe environment
3 likes10,459 views
The document discusses implementing DevOps practices in mainframe environments to foster agile development and enhance collaboration between COBOL and Java teams. It highlights the benefits of using an integrated development environment, which enables faster delivery cycles and reduced task completion times. Additionally, it emphasizes cultural changes necessary for embracing parallel development and task-oriented approaches within traditional mainframe systems.
DevOps for the IBM Mainframe environment
- 1. DevOps for the mainframe environment Establishing a model that works across enterprise IT – including mainframe systems DevOps MicroFocus.com/DevOps
- 2. Break out of a waterfall mentality to embrace Agile development Turn the way you think about the mainframe on its head. MicroFocus.com/DevOps
- 3. Build collaboration across disparate development teams Using eclipse based development framework enables COBOL and Java development teams to be work side by side and unit test together to improve collaboration, accelerate !x times, and shorten unit testing time. MicroFocus.com/DevOps
- 4. Build collaboration across operations, QA, analysts and developers New ways of working enables greater team !exibility and agility Operations QA Analysts Developers
- 5. Accelerate delivery cycles Flexible, parallel development & testing dramatically increases rates of change Tasks have been reduced from a day on the mainframe to 23 minutes using Enterprise Developer. (Steria) MicroFocus.com/DevOps An integrated development environment in Eclipse, combining Java and COBOL development.
- 6. Contemporary powerful technology Mainframe technology actually CAN keep pace with contemporary alternatives – in fact the same technology can be used for all platforms MicroFocus.com/DevOps 01 Technical Capability
- 7. Flexibility in the tooling enables culture change While agile is not typical, with greater !exibility in the tooling, a new more !exible model is possible which enables more parallel activities, and greater !exibility in terms of managing the backlog, which is the cultural building block for DevOps 02 Cultural Change MicroFocus.com/DevOps
- 8. Move from sequential to parallel development “Lights-on” no longer is the huge drain on resources, it can be accelerated as a set of tasks, and extra , new workload can be added, accelerating delivery cycles and paying o! technical debt. 03 Task Oriented MicroFocus.com/DevOps
- 9. Visit: www.microfocus.com/devops For more mainframe DevOps resources DevOps for the Mainframe Environment MicroFocus.com/DevOps