Architecture Kata "Issue Triage"

Develop a software with which a hotline can report issues to ProductOwner.

The hotline is consulted by software users in the event of a problem. If the hotline can no longer help, i.e. in its view there is a shortcoming in the software, it reports this as an issue to the ProductOwner.

As a minimum, the hotline records each issue:

  • Product - Where did the issue occur?
  • Description - What are the symptoms? What should be improved?
  • User motivation - Why should a remedy be found?
  • Notes on reproduction
  • Customer
  • Contact person at the customer
  • Abbreviation of the hotline employee
  • Date

Every hotline employee sees their reported issues. POs see all reported issues.

The POs go through these issues and assess how to proceed with them. They carry out a triage and classify the issues:

  • Red: Unusable issue, because incomprehensibly formulated
  • Yellow: There is already a workaround for the issue (which the hotline was obviously unaware of)
  • Green: Issue is generally accepted and forwarded for further planning
  • Black: Issue is not dealt with further, e.g. because it does not make economic sense

The overview of issues can be restricted by date and/or by class, e.g. only red+yellow issues in a date range or only unclassified issues.

When classifying an issue, it is noted in the issue who classified it and when. The classifier can also specify a reason and, in particular for green issues, a "weight". [1]

Statistics can be generated for a period of time with the number of issues per class per day. The statistics are exported to a CSV file in the following form:

DatumRotGelbGrünSchwarz
2.3.20143514
3.3.20147232
...

Issues can be exported to a CSV file for further processing with other tools. [2]

POs can delete all issues. Hotline employees can only delete their own unclassified issues.

Registration with the software system can be done informally.

The distinction between PO and hotline employee can be made during installation.


[1] This could be the number of users who benefit from it, or an idea of how much money could be saved or how much revenue could be generated.

[2] Multi-line fields are enclosed in apostrophes.

en_USEnglish