DevOps Mastery Program – Abstract
There are numerous DevOps training courses being offered by various vendors today, but unfortunately many of them simply focus on tools and miss the entire point of what the DevOps movement is truly about. The reality is that the overwhelming majority of successful DevOps implementations have been grass roots efforts and not top down mandates. In order for individuals to understand how to start their own grass roots campaign in their workplace, they need to truly understand the roots of DevOps, the forces behind the DevOps movement, what DevOps truly is and is not, how to make a business case for DevOps, the required building blocks of DevOps, leading DevOps practices and how to develop a plan for successfully introducing DevOps in the workplace.
The DevOps mastery program is intended for anyone working in IT/Software development who is looking not only for a more productive way to work, but would also like to introduce these practices in their workplace.
This program is offered as 10 weekly sessions lasting each 2h. You can join this session at any time (any week) and complete your 10 sessions in the order of your choice. These 10 week program keep rotating 4 times a year.
Week 1 – Laying a DevOps Foundation with TQM
Workshop – Applying Deming’s principles to Software Development – Kanban board
To fully understand the DevOps movement and where it is going requires one to recognize the principles that it is based upon. The DevOps movement draws on a foundation of Total Quality Management (TQM) which was is based upon the work of Dr. W. Edwards Deming (The father of quality) and his fourteen points, system of profound knowledge and seven deadly diseases.
By having a baseline of quality principles, we can then apply these principles to IT/Software development. It is critical to understand that DevOps is not a new way of tackling quality issues, it is simply bringing well tested principles and practices to bear on IT/Software development.
Week 2 – Understanding the DevOps Implications through Lean Manufacturing
Workshop – Theory of Constraints
The term DevOps is a popular term being thrown around the IT/Software Development industry today, but unfortunately there are often many connotations to it and it can also bring fear to many who do not understand it. The truth is that DevOps is a dramatic change to the way companies do business and how they incorporate their IT/Software Development. In order to truly understand the implications of DevOps, we have to look back at the Lean Manufacturing revolution of the 1980’s to picture this change.
Like the Lean Manufacturing revolution, DevOps requires dramatic changes in the way companies work. When looking at today’s business environment, the truth is that IT/Software development have become the factory floor for every type of business worldwide. Companies must learn that IT/Software development can no longer be treated as a sort of ticket taking group that supports the core business, instead IT/Software development is a key part of the core business.
Week 3 – History and Definition of DevOps – Understanding DevOps Measurement/Metrics and Quality
Workshop – DevOps Measurements
In this section we will explore the history of DevOps and the timeline of its existence, while also attempting to provide a definition of what DevOps means. Trying to wrap DevOps in a concrete definition is difficult, but the basics of what it is attempting to accomplish is fairly straight forward.
It is also important to not only explore, but understand the differences in how quality is seen, measured and accomplished from the perspectives of waterfall, agile and DevOps. Lastly we will wrap up this section by exploring measurements and metrics from a DevOps perspective and how it has borrowed many aspects from the agile methodology.
Week 4 – Business Case for DevOps
Workshop – Value Stream Mapping
Most companies who have successfully made the journey to DevOps started the movement from within and eventually gained senior level management support to scale to the entire organization. What this means is at some point in the DevOps journey you will have to make the business case to management and the business, in this section we will walk you through the steps to making this business case.
As we go through this section we will concentrate on the key concept of identifying waste and how tools such as value stream mapping can help identify this waste in your processes. As we identify the areas of waste in typical SDLC’s we will look at the concept of how “drift” get built into processes.
Week 5 – Building Blocks of DevOps – Culture Change
Workshop – Culture Change
One truth holds true for all companies who successfully make the journey to DevOps, they have accepted the cultural changes required in order to make the move to DevOps. There are many tool vendors and individuals who are selling the belief that if you simply install some tooling you will have DevOps, the hard truth is these companies will all fail on the journey to DevOps because they have failed to tackle the cultural changes that must be put into place in order to make the move to DevOps.
In this section we will explore traditional culture in waterfall through agile and the differences between them and DevOps. We will also explore how you make the changes necessary in DevOps as well as identifying who you should involve in your efforts to incorporate DevOps.
Week 6 – Building Blocks of DevOps – Automation
Workshop – Automated Testing
One of the key building blocks of DevOps is the need to incorporate the use of automated testing. In this section we will explore the main concept of “flipping the testing pyramid”. One of the most difficult aspects most groups, teams and individuals face in flipping the testing pyramid is making the possible transition to playing a new role in testing. In many cases automated testing requires a skill level that many quality assurance individuals do not possess, which often means that developers may have to play the role of writing automated testing. In addition, many companies and development teams have long neglected unit testing, in DevOps and in particular when flipping the testing pyramid this becomes a requirement and makes up the base of their testing.
In this section we will walk participants through the concept of flipping the testing pyramid and provide strategies for accomplishing it. In addition, this section will explore in depth the concept of adding quality gates through tools such as SonarQube and how these quality gates fit into the continuous integration process.
Week 7 – Building Blocks of DevOps – Traceability Through Specification by Example
Workshop – Specification by Example (BDD/ATDD)
DevOps requires some fundamental changes in the way software is developed and delivered, in this section we will explore these concepts. In order to create an automated pipeline companies moving to DevOps quickly discover that they need to release code in small incremental releases instead of the traditional big bang release. Another key to success is decoupling their code from traditional code release schedules in order to move code through their pipeline in an automated fashion.
In order to release this incremental code through an automated pipeline requires an emphasis on building the infrastructure to handle this. This new infrastructure has to be treated in a fashion that many companies have never experienced, that is that this infrastructure needs to be treated just like their application code. Treating infrastructure code just like application code means that this code must now be stored in a SCM, versioned/baselined and tested.
Week 8 – Additional Benefits realized through DevOps
Workshop – Andon Cord
A number of companies who have successfully made the move towards DevOps have discovered that it has brought about unexpected benefits. In this section we will take a close look at how many of these companies have discovered that instead of DevOps introducing additional security concerns, quite the opposite has happened. Many companies have found that DevOps dramatically lowers their security concerns due to the enhanced monitoring, feedback loops and ability to quickly move security fixes to production.
In addition, many DevOps companies have also discovered that DevOps leads to an tremendous strategic advantage in the form of A/B testing. With the ability to quickly move code to production, many companies are now able to run A/B tests on a daily basis, which in turn provides almost instant feedback to their business.
Week 9 – Cutting Edge DevOps Practices
Workshop – Advanced practices reading and discussion
The keys to moving towards DevOps are not a secret, in fact many of the top DevOps practitioners are very open about sharing their experiences and insight. In this section we will take an in depth look at some of the top cutting edge practices that many of these companies have put into place. We will take a very close look at the concept of “Dojos” that Target has put into place as well as looking at how a company like Amazon has incorporated the concept of Andon Cord into every phase of their business.
Week 10 – How to Introduce DevOps in your Organization
The final section of the DevOps mastery series will cover putting the previous sections into action by creating an actual plan that you can take back to your company and start your journey towards DevOps. In this section we will cover step by step the path that other individuals and companies have followed in order to get their company moving on the DevOps journey. We will take a close look at how you can start the journey by introducing simple automated smoke tests, get your agile teams to incorporate specification by example and how you will need to find a senior level sponsor in order to scale the DevOps movement throughout your company.
No Events on The List at This Time