Defect Work Flow

Future
(Defect cannot be fixed
at this time but will be
addressed in a later
deployment)

QA Failed
(QA)
Assign back to
Developer

No
No In Progress
New (Developer) Fixed
Is defect valid? Open If development (Developer)
(QA)
Assign to appointed
PM\BA\Dev Yes (Developer) Yes Yes determines it is not valid, Checked into correct QA Ready
Defect Detected Development lead
Will defect be change status to branch in Subversion.
Does defect
defect lead. (Appointed Lead should Is defect valid? (QA)
(QA) by project manager for evaluates defect and addressed? Rejected, As Designed Enter Fixed in Build pass?
meet to review assigns to appropriate or Duplicate. If more revision number.
appropriate work
defects developer on the team development research is Assigned back to defect
stream.)
needed, change status to Originator
Research Yes
Further Research No
Required
No
Research Rejected
(PM\BA\Dev As Designed or Reopen Does
Yes
Lead) Duplicate Assign back to QA Passed
Developer
defect occur
PM\BA\Dev Lead should (Developer) (QA)
(QA) consistenly?
work together to clarify is Assign back to defect
defect is valid or not Originator

No

Monitor
(Record reoccurrences
Yes of defect)
Is defect valid?

No No

Does
Yes
QA or the
Rejected End
Business
(BA) agree?
Based on research by
the BA it was deemed
this is not a development
defect. BA should now
update the defect
comments indicating the
reason the defect is
being rejected as well as
what documentation is
being updated.

The BA should also work

with the QA analyst to
ensure test cases are
updated to reflect the
behavior.