Skip to main content

DevOps Stakeholders – Who Are They?

IT professionals attending the DevOps FND Certification class offered by the DevOps Campus at ITSM Academy are sometimes surprised to discover that DevOps in not just about Dev and Ops.

The DevOps pipeline and value stream for the continuous delivery of products and services mandates that an integration of requirements and controls be orchestrated in such a way that speed and value are achieved. DevOps extends far beyond software developers and IT operations.


One way to consider the stakeholders for DevOps:

Dev Includes all people involved in developing software products and services including but not exclusive to:
  • Architects, business representatives, customers, product owners, project managers, quality assurance (QA), testers and analysts, suppliers …
Ops Includes all people involved in delivering and managing software products and services including but not exclusive to:
  • ·Information security professionals, systems engineers, system administrators, IT operations engineers, release engineers, database administrators (DBAs), network engineers, support professionals, third party vendors and suppliers…
The challenge for any DevOps initiative is how to include all systems necessary to incorporate the activities, requirements and roles that these stakeholders represent. We must radically shift our thinking. Service providers need to understand that it's not what we are doing that has to change but need to consider how we do it. We still need to deliver services that deliver value to our customers. The old way of doing things does not work in today's world. How we do things must be accelerated in order to perform. Our mission should be to clear the backlog of requests for new and changed services and deliver robust, stable services at the speed of a keystroke.

Use this link for more information on DevOps Foundation and other DevOps courses available.



Comments

Truly welcome this great post that you have accommodated us. Extraordinary site and an incredible point also. I am truly astonished to understand this. It's great substance about stakeholder. Andrew Barnett Fort Lauderdale

Popular posts from this blog

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 than 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

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 th