devops for the ibm mainframe environment

9
DevOps for the mainframe environment Establishing a model that works across enterprise IT – including mainframe systems DevOps MicroFocus.com/DevOps

Upload: micro-focus

Post on 15-Apr-2017

9.295 views

Category:

Technology


1 download

TRANSCRIPT

Page 1: DevOps for the IBM Mainframe environment

DevOps for the mainframe environmentEstablishing a model that works across enterprise IT –including mainframe systems

DevOps

MicroFocus.com/DevOps

Page 2: DevOps for the IBM Mainframe environment

Break out of a waterfall mentality to embrace Agile developmentTurn the way you think about the mainframe on its head.

MicroFocus.com/DevOps

Page 3: DevOps for the IBM Mainframe environment

Build collaboration across disparate development teamsUsing 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

Page 4: DevOps for the IBM Mainframe environment

Build collaboration across operations, QA, analysts and developersNew ways of working enables greater team !exibility and agility

Operations

QA Analysts

Developers

Page 5: DevOps for the IBM Mainframe environment

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.

Page 6: DevOps for the IBM Mainframe environment

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

Page 7: DevOps for the IBM Mainframe environment

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

Page 8: DevOps for the IBM Mainframe environment

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

Page 9: DevOps for the IBM Mainframe environment

Visit: www.microfocus.com/devopsFor more mainframe DevOps resourcesDevOps for the Mainframe Environment

MicroFocus.com/DevOps