IT TECHOLOGY

⌘K
  1. Home
  2. Docs
  3. IT TECHOLOGY
  4. AGILE SOFTWARE DEVELOPMEN...
  5. PROBLEM RESOLUTION AND TROUBLESHOOTING

PROBLEM RESOLUTION AND TROUBLESHOOTING

  • as soon as you get an error msg , store the error msg txt into a tmp file , so that you could later on use it …
  • try just to quickly fix it without changing the source code of the proejct you are working on
    • if you can – good
    • if it was something worth mentioning , write a small how-to in confluence
    • if cannot not proceed
  • REGISTER the bug in Trello , if it took you longer than 15 min to resolve
    • describe it properly – what did you try to achieve
    • what did you run
    • what did you expect
    • what did actually happen
    • attach all the evidences
  • try to resolve the bug in your own for at least 1h
    • if you resolve the bug and it requires change in the src code ..
    • if you manage to resolve it in under 1h make a new feature branch and PR
    • if the fix was related to your machine confs etc. write a msg in slack / article in confluence
  • If you cannot resolve the bug assign it to the PM of the project ( quite often )
  • Now you should have clear conscious – you can continue with your other work entities
  • Be prepared to be asked for more details on the bug

In short: We cannot help you , if you don’t tell us !

+

Nobody is left behind – we are all in this together – and we all most help each other to go forward !

Articles

How can we help?