It's all about the answers!

Ask a question

using RQM for large organizations


john liu (567) | asked Jul 17 '14, 8:58 a.m.
 For large organizations that support both waterfall, agile processes and anything in between, are there recommendations on how many project areas they should have (by division, by product, by application, by project)?  When you have a lot of test artifacts inside a project area, what are some of the best practices for organizing them so that they are easy to locate and manage?  Thanks!

2 answers



permanent link
David Mehaffy (90122535) | answered Jul 17 '14, 11:54 a.m.
JAZZ DEVELOPER
 Well the answer is it depends.  We have a 1000+ users in a single project area in several cases and other project areas with less than 100 users in them.  The size depends a lot on how much sharing of artifacts you want.  We have the large project areas because we started out in RQM pre 1.0 and then you could only have one project area.  In that case we have common test environments and it worked very nicely because we could share requirements, test environments and test cases.  In other cases we spun of separate project areas where the test environment was unique like Japanese locale testing which did not have anything in common with other testing.

For organization, categories are your friend.  We use them to sort by function for example so we can look at execution status by functional area, etc.  So as long as you have a good category structure large project areas are manageable.  I would also recommend not going more than 3 levels deep as it will become unmanageable over time.

Dave

permanent link
Georg Kellner (80937092) | answered Jul 18 '14, 4:41 a.m.
There are no general recommendations to the project areas, as thew wording project, product ... differs from company to company.

As David mentioned, if projects/products are sharing the same testartifacts, they can be bundled in one project area.
If things are completely different, several project areas are okay.
There might be also project areas based on IT security issues. Some external partners might be allows to only see the project relevant data, an own area is needed.

Regarding the overview:
A naming convention can also help.
We have a project, using TPm: for Master TestPlans and TPc: for Child TestPlans.
In 5.0 there is the possibility to have unique names in the test artifacts. This might help to avoid misunderstanding.
Think about using team structures also, this will also help to get the overview.

greetings georg.

Your answer


Register or to post your answer.