| Table of Contents |
|---|
...
POs will CLOSE stories after QA MQA complete their testing (we should never close untested stories!). For example, say the PO reviewed and approved the story in Snapshot, then they may want to look at it again in Sprint Test after QA MQA is finished before closing it, OR they can review the results of QA MQA testing and if no bugs have been reported the PO can go ahead and close the story. If bugs have been reported, then the PO needs to decide whether the found bugs need to be fixed before closing the story or the story can be released as is (so the PO then goes ahead and closes the story). In the latter case, the bugs found will be deferred to the next release.
...
This initiative is to improve our automated test coverage significantly. Increasing automation test coverage is crucial as it has been proven to be a reliable and efficient method for detecting bugs at an earlier stage of the testing process.
Starting: Sprint 170, automation work will be managed centrally.
...