15.2.07
HP Mercury Quality Center Enterprise Test Projects
Many Quality Center (QC) sites start building projects for each enterprise project that they have on the release timetable at any given time. This leads to siloed projects from a testing perspective and the Dashboard doesn't usually solve the problem of looking at an overall status of testing. Enter the custom report. I've built many spreadsheets that run cross project queries to get the status of test sets and defects. The problem is that each time I do this I have to deal odd ball customizations.
When is it time to move all those tiny projects into a new large project? How do you decide what to do with the customizations that cake up onto each project like barnacles on boat? The answer is take the time and hash out the best common design with liasons to each team when you decide to merge projects. Then schedule about 12 hours outage time to move projects together. More or less time can be taken depending on how large the projects are. I recommend documenting the process (ie. all the SQL queries involved and custom fields to be created) and have a dress rehearsal.
The question of when to merge projects can be answered pretty easily. Do it if:
1. You need to have defects tracked in one place
2. You need to bring multiple projects closer to each other because future collaboration is mission critical.
3. You need a good reason to redesign defect dialogs
It will take about 2 months to do the whole project depending on the availability of people involved.
When is it time to move all those tiny projects into a new large project? How do you decide what to do with the customizations that cake up onto each project like barnacles on boat? The answer is take the time and hash out the best common design with liasons to each team when you decide to merge projects. Then schedule about 12 hours outage time to move projects together. More or less time can be taken depending on how large the projects are. I recommend documenting the process (ie. all the SQL queries involved and custom fields to be created) and have a dress rehearsal.
The question of when to merge projects can be answered pretty easily. Do it if:
1. You need to have defects tracked in one place
2. You need to bring multiple projects closer to each other because future collaboration is mission critical.
3. You need a good reason to redesign defect dialogs
It will take about 2 months to do the whole project depending on the availability of people involved.
// posted by Chris Emerson @ 17:02 
Subscribe to Posts [Atom]