WIP
Problem: Bugs must not change scope - common to see a bug and it morphs into improvements, other changes.
Fix: Raise new bug. Don't keep amending and adding new features.
Problem: Team testers/automation testers do not understand the requirement. Cause by the User Story (US) or bug being ambiguous and Acceptance Criteria (AC)
Fix: Ensure User Stories are in a standard format i.e. "As a <>, I want to <>, so that <>.". Ensure Gherkin is used for AC (Scenario, Given, When, Then, and preferably more than 1 AC per user story. Could have: Annotate diagrams to clearly convey artefact information. Also a narrated recording for bugs. This could be the person recording the bug, the person that fixed the bug as proof to increase understanding.
0 comments:
Post a Comment