Priority and Difficulty attributes - How to use properly?
Are these values and their meanings to be established by your organization? if this is the case, but hasn't and wont happen, how can these be generically defined?
Whose "Priority" (the business area i assume?) "Difficulty" of what? |
One answer
These are really just sample attributes, so you would want to customize your project to have attributes that make sense to you... you can add your own and delete any default ones that you don't use. You can also provide a description to provide more details to your users.
My guess is that "Difficulty" is meant to indicate difficulty of implementing a requirement and "Priority" is meant to indicate the business priority of the requirement.
Comments 
Ralph Schoon
commented Apr 28 '14, 12:19 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Agreed. Typically this is defined by the user. It is also necessary to define who can change the value. Severity is usually e.g. used by the user that files a defect to express how he is impacted. In the case of Jazz.net Priority is something that the Jazz development would set.
|
Comments
Not sure what you are asking here. You might want to add more information to give people the chance to provide feedback.
Artifacts (e.g., business rules) have attributes "Priority" and "Difficulty".
Does a definition exist for each? Whose priority? Difficulty of what?, etc.