The purpose of categories is to automate the mapping of work items to
team areas. So the guiding principle of category design is to create
categories that satisfy these two requirements:
- the work item creator will know what category to pick
- each category can be logically mapped to a particular team area

So one thing a good category design depends on is what your work item
submitters will understand (if they are developers, then logical
architecture might be OK, but if they are end users, then it should be
something the end user would know, such as what end-user operation it is
related to).

Cheers,
Geoff

jleone wrote:

Hello,

I can't seem to find resources that would explain the "best
practices" for defining categories? Should the be based off the
logical architecture of the software?

One thing that might influence this decision would be the "Guess
Category" feature. What does RTC take into account when making
a guess?