Skip to main content

Who needs to be informed and knowledgeable about DevOps Test Engineering?

Testing starts with the first line of code!  It is NOT a downstream activity. DevOps testing has a critical role to play in a Continuous Delivery Pipeline. Without integrated testing DevOps simply will not work!  With the advent of DevOps and the movement to breakdown silos between developers, QA, security, and operations, it becomes critically important that all members of an IT team - regardless of what tools they use, or role they play - understand the essentials of testing.

Every member of your development team should also integrate to ensure Compliance and Audit outcomes!  It is a new world.  In this new world, we can leverage from existing but must be open to walking through new doors of opportunity.

Understanding traditional test strategies is helpful but when and where, and most importantly how we proceed with our test strategy must shift.  Knowing how to code is not enough, Quality Assurance in and of itself is not enough.  We cannot afford to have our products and services fail and we certainly do not want them to fail publicly. 

Anyone involved in defining or deploying a DevOps testing strategy and those orchestrating and automating a Continuous Delivery Pipeline.

That includes:
  • Quality assurance managers
  • Testers and quality assurance teams
  • Software engineers and DevOps engineers
  • IT managers
  • Project managers
  • Release managers and delivery staff
  • Maintenance and support staff
  • Anyone involved in testing tool selection
  • And if you are reading this, YOU!
This is an amazing time of opportunity in the IT Industry.  We do not have to give up stability and reliability for speed.  You and your staff can optimize your career path and change the direction of your entire organization.  That direction leads to real outcomes that benefit speed to value, and customer satisfaction at a lower cost.  It can be done!


Comments

Popular posts from this blog

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

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

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