DevOps - Driving Mainframe Agility

Applying DevOps principles and practices will be needed to ensure the DevOps values for Culture, Automation, Measurement and Sharing (CAMS). As major industries consider how to optimize for 2016, busting out of silos should be at the top of their list. This is true in all areas of service management and includes mainframe systems and applications.

Mainframe application and system development, like all areas of development, face many obstacles that include broken processes, obsolete tools and the common us vs. them mentality. Mainframe systems remain crucial for critical business knowledge and back-end support for customer engagement. What are service providers going to do when the mainframe developers retire or move to other positions? We have seen decades of progress on many platforms but in many cases mainframe code is still managed by siloed teams. Even so, things are moving in the right direction to increase and optimize the value stream for the development, deployment and ongoing support for mainframe solutions.

Compuware Corporation, a mainframe-dedicated software company, recently announced far-reaching partnerships, a major acquisition, and continued innovation within its own industry-leading software portfolio—all in support of a game-changing initiative that will empower customers to incorporate mainframe applications into their broader cross-platform Agile/DevOps processes.

In the Jan 5, 2016 Eweek article Darry K. Taft quotes AppDynamics President and CEO David Wadhwani who said, “At AppDynamics, our goal is to provide enterprise IT with one platform for unified monitoring, DevOps collaboration, and application analytics.

The approach for adopting a DevOps culture for mainframe software and system solutions is the same as any other industry and begins with getting a clear understanding of the business “Why”. Gleaning from John Kotter’s eight steps “Create a sense of urgency” broadcast it out and keep the momentum going by:

Getting the right people together – ensure core stakeholders are engaged; particularly early adopters who are committed to experimentation and learning.

Get everyone on the same page – seek to understand each other’s perspectives and concerns, determine what outcomes you want to achieve and set measurable goals – be realistic!

Build capabilities that lead to lasting change – use education to introduce a common vocabulary, provide ongoing, just in time training, leverage early adopters and informal networks of peer motivators, build trust through transparency, and generate and celebrate short-term wins.

Focus on critical behaviors - every culture has behaviors that help enable change.

Experiment and learn – prioritize improvement opportunities, take a holistic approach; learn and share vs. mandating.

Consolidate gains and produce more change – in the spirit of transparency, communicate successes, failures and lessons learned. Document and make available reusable artifacts and measurements. Continuously invest in needed education, training and technologies, and expand your cycles of improvement.

And last but not least be a change champion and TAKE ACTION. It’s time to mainstream the mainframe!

For further details and information regarding DevOps training and certification:

DevOps Campus

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

Search