O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Poka yoke: The Science of Mistake Proofing in Software

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
Crucible Product Overview
Crucible Product Overview
Carregando em…3
×

Confira estes a seguir

1 de 23 Anúncio

Poka yoke: The Science of Mistake Proofing in Software

Baixar para ler offline

Presentation on Poka Yoke in Software which was delivered by Dhaval Doshi and Gurpreet Luthra at ThoughtWorks xConf in July 2012.

For details refer to Blog Post:

http://techie-notebook.blogspot.in/2012/07/poka-yoke-applying-mistake-proofing-to.html

Presentation on Poka Yoke in Software which was delivered by Dhaval Doshi and Gurpreet Luthra at ThoughtWorks xConf in July 2012.

For details refer to Blog Post:

http://techie-notebook.blogspot.in/2012/07/poka-yoke-applying-mistake-proofing-to.html

Anúncio
Anúncio

Mais Conteúdo rRelacionado

Semelhante a Poka yoke: The Science of Mistake Proofing in Software (20)

Anúncio

Mais recentes (20)

Anúncio

Poka yoke: The Science of Mistake Proofing in Software

  1. 1. POKA YOKE The Science of Mistake Proofing Gurpreet Luthra & Dhaval Doshi (ThoughtWorks xConf – Bangalore – July 2012)
  2. 2. What is POKA YOKE ?
  3. 3. What is POKA YOKE ? Poka YOKE Inadvertent Mistake Prevent
  4. 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. 5. Types of Poka Yoke devices Control Warning
  6. 6. Pin Index Safety System (PISS)
  7. 7. Buckle Up!
  8. 8. Poka Yoke / Mistake Proofing In Software
  9. 9. UI Mistake Proofing
  10. 10. UI Mistake Proofing
  11. 11. UI Mistake Proofing
  12. 12. Radiators Unit Tests IDEs
  13. 13. Compilers Pre-commit • Commit Message • Developer Names • New Files missed • Build is RED check • Run Unit Tests Auto Save • Check-in to VCS
  14. 14. Architectural Controls HttpSession No updates on GET Context specific injection
  15. 15. Architectural Controls Run Under Least Privilege Primitives Vs Types Circuit Breaker
  16. 16. Some more examples… Password Log Check Live Data Testing Keyboard Shortcuts
  17. 17. What do you think?
  18. 18. Pragmatic Mistake Proofing Feedback Blast Radius
  19. 19. Distributed “Agile” !! Remote Teams Long Running Projects Legacy & Complex Codebase Team Attrition
  20. 20. Qualities of a Good Poka Yoke Early Precise Painless Simple
  21. 21. Instead of a BOLD font email, Choose a POKA YOKE Thank You

Notas do Editor

  • Introduce
  • Process is designed in a manner that you cannot make mistakes – CONTROL..WARNING: Will immediately catch the mistake and give you a warning.
  • PART OF THE PROCESS. While pushing, automatically with the weight of the person – it would move forward.
  • Control poke wasn’t a good idea here!
  • 2 MINUTESPassword entered: Passw0rd
  • 2 MINUTESPassword entered: Passw0rd
  • 2 MINUTESPassword entered: Passw0rd
  • 1 MINUTE
  • 2 MINUTE
  • 3 MINUTES
  • 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.
  • 4 MINUTES
  • 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

×