Bugs and non-technical client
0 likes123 views
The document outlines best practices for non-technical clients to report bugs and for teams to manage those reports effectively. It emphasizes using a bug reporting system, effective communication through tools like Slack, and assigning responsibilities for bug fixes. Additionally, it highlights the importance of automated testing and client involvement in the testing process.
Bugs and non-technical client
- 1. A noN-technical client & THE BUGS By Irek skrobis Lead developer @ SELLEO
- 2. agenda
- 6. 1. Client
- 7. × url Client: reporting bugs
- 8. × url × screenshot Client: reporting bugs
- 9. × url × screenshot × description Client: reporting bugs
- 10. × use a bug reporting system Client: reporting bugs
- 11. × use a bug reporting system × use Slack/HipChat (if not urgent) Client: reporting bugs
- 12. × use a bug reporting system × use Slack/HipChat (if not urgent) × create a bug specific channel Client: reporting bugs
- 13. × use a bug reporting system × use Slack/HipChat (if not urgent) × create a bug specific channel × make sure each dev has access to it :) Client: reporting bugs
- 14. × use a bug reporting system × use Slack/HipChat (if not urgent) × create a bug specific channel × make sure each dev has access to it :) × use @all / @channel mention Client: reporting bugs
- 15. × use a bug reporting system × use Slack/HipChat (if not urgent) × create a bug specific channel × make sure each dev has access to it :) × use @all / @channel mention × send an email (if urgent) Client: reporting bugs
- 16. × explain to the client what bugs are urgent and what bugs are NOT urgent Client: reporting bugs
- 17. 2. Team
- 18. × create an automated tests suite TEAM: bugs prevention
- 19. × create an automated tests suite × use the continuous integration tools TEAM: bugs prevention
- 20. × create an automated tests suite × use the continuous integration tools × the other team member should test a new feature before it go to staging TEAM: bugs prevention
- 21. × create an automated tests suite × use the continuous integration tools × the other team member should test a new feature before it go to staging × let the client test the feature on the staging TEAM: bugs prevention
- 22. × daily stand ups (if possible) expose all team members to THE client (HOW?)
- 23. × daily stand ups (if possible) × each team member should ask questions to the client by himself expose all team members to THE client (HOW?)
- 24. × daily stand ups (if possible) × each team member should ask questions to the client by himself × redirect the client to a correct team member in case of any questions expose all team members to THE client (HOW?)
- 25. × easier for the client to ask for help expose all team members to THE client (why?)
- 26. × easier for the client to ask for help × shorten the chain of command expose all team members to THE client (why?)
- 27. × assign someone to each bug during the working hours RESPONSIBILITY
- 28. × assign someone to each bug during the working hours × make someone responsible for fixing bugs on the production after the working hours (especially after a big deployment) RESPONSIBILITY
- 29. 3. bugs
- 30. × explain how the feature works IS IT A BUG OR IS IT A FEATURE?
- 31. × explain how the feature works × prepare an instruction how to test it IS IT A BUG OR IS IT A FEATURE?
- 32. × explain how the feature works × prepare an instruction how to test it × ask for testing it on the staging IS IT A BUG OR IS IT A FEATURE?
- 33. × explain how the feature works × prepare an instruction how to test it × ask for testing it on the staging × ask for testing it on the production IS IT A BUG OR IS IT A FEATURE?
- 34. don't trust that the client Actually tested the feature :)
- 35. × answer as soon as possible IT IS A BUG...
- 36. × answer as soon as possible × explain: IT IS A BUG...
- 37. × answer as soon as possible × explain: × what happened IT IS A BUG...
- 38. × answer as soon as possible × explain: × what happened × the possibility of next occurrence IT IS A BUG...
- 39. × answer as soon as possible × explain: × what happened × the possibility of next occurrence × what you are going to do IT IS A BUG...
- 40. × answer as soon as possible × explain: × what happened × the possibility of next occurrence × what you are going to do × when you are going to fix it IT IS A BUG...
- 41. × fix ALL errors ASAP (even not important one) before the client notice them USE A BUG REPORTING SYSTEM TO YOUR ADVANTAGE
- 42. × fix ALL errors ASAP (even not important one) before the client notice them × hide errors that are not dependent on you (for example the ones caused by crawlers) USE A BUG REPORTING SYSTEM TO YOUR ADVANTAGE
- 44. THANKS!LIVE LONG AND PROSPER IREK SKROBIS @ireneuszskrobis