Integration - Mecury Quality Center - Defect Tracker

Edit Subject

We use QC's Requirements module for storing our product requirements (epics, user stories, etc) and currently are importing those via Excel into Scrumworks for backlog prioritization and task assignment.

We are looking forward to this feature. (It is actually one of our main requirements). What is the minimum of integration is a link between features and the tests developed for this feature. A similar link between task and test would be great but not a basic requirement.

Unlike Manteli our focal point is ScrumWorks. This is where we describe user stories, requirements etc etc. Therefore it would be great to have a simple way of transferring this information directly to QC.

I strongly agree with both entries above. Here we use scrumworks daily and create quite a bit of content in it during planning. But, our teams from that point on start to use one side that fits their needs, and before too long, it is difficult to see the big picture. QA uses TD to manage tests, test execution, and defects. if we could keep the two tools synced a bit on the task level, im certain it would help our teams.

Our needs are quite simple. Allow a scrum sprint ( goals and tasks ) to be mirrored into TD requirments from which reqs can spawn many tests in verification of it. The abiltiy to also link a task to a Defect in TD would be great as well.

fingers crossed for a solution!

Have you tried exporting the User Stories from ScrumWorks into Excel and importing those into QC using the HP Excel Add-in?
Works for us at least, even though we're doing it into the opposite direction :). Ofcourse an automated solution would be better.

We played with the excel addin a little, it but it had little effect in simplifying things as the sprint continued...

I think from the user side, a link to TD could be quite easy to use. A user would simply add a <sync> flag to a task, signaling that it should be mirrored with the defined 'recipie'.

The 'recipie' contains connection details, and sets defaults for a scrum proejct on how and where to mirror flagged items. ( think: where in TD Req tree or Test Tree to call 'root' for mirrored entities in a project sprint ) and possibly setting some default values or other sync settings, as needed.

Then between SW and TD, when either side of a sync-linked item is edited for content ( added detail or implementation status, etc ) the other side would get the update as well to the mapped fields in the recipie.

</sync>

Our QA dept uses QC. It would be really nice to give our product owner 1 single tool to use. Don't really care which. Having Bugs show up as tasks for the backlog item they belong too would be nice too.

Hi Jpeckham,

I don't have anything to note here specifically about ScrumWorks. However, this is something that I do have some news on.

Have a look at this: http://www.collab.net/products/integr...

ScrumWorks now has a full integration to Teamforge, and by extension Quality Center. I don't personally have full information on how the Teamforge-QC integration works, but I can tell you that the Teamforge-ScrumWorks integration is very smooth.

From our perspective here on the ScrumWorks team this integration addresses a number of feature requests we have had. If you are interested in some specifics just toss me an email: cbrown@collab.net

I am a bit behind today (as I was out this past week) but I should be able to get you a response before mid-week.