required to accomplish the job– I would suggest to use the “Tools” term which includes both the hardware (devs machines, CI server) and software (i.e.
Machines: Any equipment, computers, tools, etc.Methods: How the process is performed and the specific requirements for doing it, such as policies, procedures, rules, regulations and laws – I think the “Process” term is better suited for software development.People: Anyone involved with the process – no need to change, there are many people-related problems in IT.At first I thought that I will have to modify the original categories, but after a while it occurred to me, that no major changes, but rather a refactoring of names is required (the descriptions were copied from Wikipedia article): I have to say that I’ve enjoyed this little experiment. I wanted to try it myself, so I choose an arbitrary (but quite common) problem – “low quality of software” – and tried to use Ishikawa diagram to find the causes. (I will not explain Ishikawa diagram in this post, so please have a look at Wikipedia description if it does not ring any bells for you). And I started to wonder whether it makes sense to use it to diagnose the issues related to the production of software. Today I have learned about Ishikawa diagram (AKA fishbone diagrams, herringbone diagrams, cause-and-effect diagrams, or Fishikawa).