Best Practice for Project Management in RQM
We are considering a new approach to arranging our projects in RQM. We average around 5 large to medium projects a year and several service requests. We were thinking about creating a Project for each project (that will display in the drop down). We would like to configure each Project with our categories, team members, etc.... We would also like to configure each Project with RTC and RRC.
We would like some advise (pros, cons, past experience, what has worked for you, what has not worked for you, any suggestions).
Renee |
3 answers
I haven't found a single source answer for this (which isn't unexpected) but these links seem like a good starting point for investigation:
http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0/topic/com.ibm.rational.test.qm.doc/topics/c_workflows_guidance.html?resultof=%22%62%65%73%74%22%20%22%70%72%61%63%74%69%63%65%73%22%20%22%70%72%61%63%74%69%63%22%20 http://www.ibm.com/developerworks/rational/practices/test_mgmnt/ Hopefully the community at large will eventually respond with their practical anecdotes. |
|
Here's another interesting article:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/dchadwick/entry/jazz_products_and_project_areas35?lang=en |
|
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.
Comments
we are currently on 3.0.1.2 but will be upgrading to 4.0 in a month