Defect manangement flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2019 08:23 AM
We're trying to start making use of defects and enhancements in our development workflow.
I don't see documentation explaining how the process flow is supposed to work. I'm aware one can create stories from enhancements and defects. However, for defects there's also a process flow of Draft->Scoping->Awaiting Approval->Work In Progress->Testing Q/A->Deployment->Closed
It appears that the "workflow" simply follows the state of the defect. There's no place to review new defects, no real approval process, etc.
I'm curious to see how others are using enhancements and defects in their agile workflow. Does your scrum master just daily look for new defects and move them to the "scoping state?" Do they move them past "awaiting approval" once an associated story has been created? Do they go back and move them into "work in progress" once the story has been put into the active scrum? Etc.
Just interested to see how others are utilizing these concepts.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2019 09:47 AM
Currently we're using Defects and Enhancements. For Defects, once created they email the SN team as they take priority over enhancement work. Given we've already deployed and it's not working or we forgot about this or that, it needs to be done pretty quick. Once assigned they are moved to Scoping but we don't require approvals on Defects but do follow the other states for handling them. After being tested by another member of the SN team, we release it for testing to Ops team so they can confirm this is what they wanted etc.
Enhancements require CAB approval before deploying.
