There are many different approaches to developing software and lots of talk about which one is the best software development methodology. Being a student of our industry, we have experimented with many and come to recognise there is a meta-methodology that could be used to describe them all. So, for Jidoka, it is important to set a few parameters and specify what parts of these other methodologies we keep, and what parts we leave behind.
| Methodology | What do we take? | What do we leave behind? | Summary |
| Scrum |
Huddles Ceremonies Backlog Definitions |
Sprints Story points Velocity |
The Scrum meeting pulse (huddles, ceremonies, etc) is amazing for communication and the attention to backlog refinement raises project quality. Constant sprinting is tiring and story points are a waste as they get converted to time anyway. Velocity does not consider mass (size) of the system, momentum does. |
| Kanban |
Kanban board Checklists Continuous flow |
WIP limits Specialised teams Handover loss |
The continuous flow of work across a Kanban board can far outpace other approaches that are stop/starting. However, the balanced queues of WIP limits lead to specialised teams with all the problems of waterfall reemerging. |
| DavOps |
Pipelines Removing barriers |
Rules complexity Burdensome governance |
Breaking down the barriers between development and operations using pipelines to automate and scale is empowering. But some practitioners use this to enforce overly complex company policies and can rebuild that wall that was originally torn down |
Learn about our process and solutions:
All Rights Reserved. 2024 WorkingMouse Pty Ltd. All Rights Reserved.
