Poka yoke: The Science of Mistake Proofing in Software
Download as PPTX, PDF7 likes5,281 views
Poka Yoke is a methodology aimed at mistake-proofing manufacturing and software processes to prevent inadvertent errors. It includes various devices and techniques to ensure mistakes are either impossible or quickly rectified, such as control systems and architectural guidelines. Key qualities of effective Poka Yoke solutions involve being early, precise, painless, and simple.
Poka yoke: The Science of Mistake Proofing in Software
- 1. POKA YOKE The Science of Mistake Proofing Gurpreet Luthra & Dhaval Doshi (ThoughtWorks xConf – Bangalore – July 2012)
- 2. What is POKA YOKE ?
- 3. What is POKA YOKE ? Poka YOKE Inadvertent Mistake Prevent
- 4. What is POKA YOKE ? The essential idea of Poke Yoke is to mistake proof the manufacturing process --- so that mistakes cannot be made or can be caught/fixed quickly.
- 5. Types of Poka Yoke devices Control Warning
- 7. Pin Index Safety System (PISS)
- 9. Buckle Up!
- 10. Poka Yoke / Mistake Proofing In Software
- 14. Radiators Unit Tests IDEs
- 15. Compilers Pre-commit • Commit Message • Developer Names • New Files missed • Build is RED check • Run Unit Tests Auto Save • Check-in to VCS
- 16. Architectural Controls HttpSession No updates on GET Context specific injection
- 17. Architectural Controls Run Under Least Privilege Primitives Vs Types Circuit Breaker
- 18. Some more examples… Password Log Check Live Data Testing Keyboard Shortcuts
- 19. What do you think?
- 20. Pragmatic Mistake Proofing Feedback Blast Radius
- 21. Distributed “Agile” !! Remote Teams Long Running Projects Legacy & Complex Codebase Team Attrition
- 22. Qualities of a Good Poka Yoke Early Precise Painless Simple
- 23. Instead of a BOLD font email, Choose a POKA YOKE Thank You
Editor's Notes
- #2: Introduce
- #6: Process is designed in a manner that you cannot make mistakes – CONTROL..WARNING: Will immediately catch the mistake and give you a warning.
- #9: PART OF THE PROCESS. While pushing, automatically with the weight of the person – it would move forward.
- #11: Control poke wasn’t a good idea here!
- #13: 2 MINUTESPassword entered: Passw0rd
- #14: 2 MINUTESPassword entered: Passw0rd
- #15: 2 MINUTESPassword entered: Passw0rd
- #16: 1 MINUTE
- #17: 2 MINUTE
- #18: 3 MINUTES
- #19: 4 MINUTESnstead of passing Primitives around, pass “Types” like money, so that you can control what operations can be performed on the data. If you couple it with immutability, then you can be sure that intermediate layers don’t inadvertently modify the object.
- #20: 4 MINUTES
- #21: Instead of passing Primitives around, pass “Types” like money, so that you can control what operations can be performed on the data. If you couple it with immutability, then you can be sure that intermediate layers don’t inadvertently modify the object.3 MINUTES