Looking for information on Work Item Categories
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? |
Accepted answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Feb 13 '10, 12:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
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, Ralph Schoon selected this answer as the correct answer
Comments
frederick carter
commented Aug 13 '12, 5:06 p.m.
great answer any examples you can point to? . especially for iterative waterfall projects? for RUP projects?
Andrew Codrington
commented Aug 14 '12, 10:46 a.m.
Here's a link to a project that uses a few categories and teams: https://jazz.net/jazz/admin#action=com.ibm.team.process.editProjectArea&itemId=_1w8aQEmJEduIY7C8B09Hyw |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.