Selecting the proper methodology for each type of project is key when leading changes. In the industrial engineering world, changes are driven by the Improvement Model that is often referred to as PDCA (Plan, Do, Check, Act). The strength of this approach is a scientific problem-solving mindset and the numerous tools born to solve common types of problems.
Over the years, Lean and Six Sigmas practitioners have built an impressive library of toolboxes (A3, Value Stream Mapping, 5S, Kanban, and so on).
I believe that a lot of those toolboxes could be repurposed to serve the DevOps culture and methodologies. This is my attempt.
So for not that much. The plan is to write a couple article on the subject and later create toolbox too share problem-solving solutions on the same topics.
For now I will keep updating this page with my latest articles.
- SMART: How to Build a “Smarter” DevOps Roadmap — The SMART Maturity Assessment Method
- 5S: How to Reduce Waste and Increase Productivity in Software Development?
- VSM: How to Maximise the Value of your Software Development Process?
- TAKT time
- Pull system (Kanban)
- Continuous flow
- Kaizen
- Supermarket
- Production levelling
- Work standardisation
- Pacemaker process
- Constant work in progress reduction
- Single piece flow
- FIFO
- Continuous improvement
- Heijunka box
- Cellular manufacturing
- SMED
- Total productive maintenance
- Just in time
- Poka yoke
References: What is Kata A cross-sector review on the use of value stream mapping