Testers and QA Manger in my organisation would like to strengthen collaboration and transparency within Agile teams, what is an essence of high-performing Agile teams. To improve the prioritization and making decision, each requirement like: Feature, User Story and tasks should be clearly tagged on the Kanban Board if at least one test is connected to the requirement, if so, what is the outcome from last test execution associated to the requirement.
Requirement Statuses could behave with following logic:
'CONFIDENT' – requirement has been successfully and fully validated; all the Tests associated with the Requirement are PASSED
'RISKY' – requirement is unsuccessfully validated; at least one Test associated with the Requirement is FAILED
'UNDER EVALUATION'– requirement has not been validated completely; at least one Test associated with the Requirement is TODO or ABORTED and there are no Tests with status FAILED
'UNCOVERED' – requirement is not covered with tests; the Requirement has no Tests associated with it
|I would like...||see on Kanban Boards in Jira view which requirements have been covered by test(s), if so, what is the outcome from test execution on the given requirement|
|So that I...||entire Agile Team and Product Owner has inside into clear picture on residual risks and quality of developing features and user stories|