08-08-2013 12:43 PM - edited 08-08-2013 01:01 PM
In large organizations where QA teams are heavy QC/ALM users with established defect workflows, synchronizing defects with Agile Manager is very attractive to both Dev and QA. However, if the status-based defect workflow can't be replicated in Agile Manager, this inhibits process enforcement and leads to undesirable consequences. We'd like to see the ability to have status-based defect workflow in Agile Manager, similar to what is in QC/ALM today.
08-10-2013 10:20 AM
Thank you for the this enhancement request.
Could you elaborate about the following points:
- Generally in Agile the QA should be part of the team and the definition of done of a user story should also cover testing the user story. Could you share how the organization that you are referring to structure their QA?
- As I mentioned above, user stories should become done only once they are tested and the test passed. It means that defects that are opened during a sprint should be resolved by the Agile team during the sprint. As Agile empowers communication over processes, defects should be lightly managed and quickly resolved as part of the inherent sprint ceremonies, such as daily meetings and sprint planning meetings. In this context, can you share the defects statuses and workflow that you were referring to?
08-11-2013 02:57 PM
On point 1, QA is continuing to work in QC since this is the tool they are most familiar with and it is where test cases are designed and run, etc.
On point 2, the entire team is already accustomed to working according to the defect workflow they have defined in QC. They do not want to change this. This is why they are interested in the AGM/QC integration to begin with.
10-04-2013 02:39 PM
My team has had the same issues. The status and business logic in QC does not match that in AGM. As a result, we've given up on using AGM for tracking defects.