How a Tester Can Help Improve the Quality of Requirements
summary
Argues that testers improve requirements by making them testable and measurable and adding concrete acceptance criteria, shows concrete templates (EARS and ISO‑style syntax) and modeling like UML, demonstrates tools and artifacts: Gyra tickets, Confluence pages, mirror stickies, mockup links and traceable error codes, recommends Behavior driven development and use‑case scenarios, points out ambiguous examples (“system shall generate transaction received”) and reports that co‑creating requirements with the team replaces slow formal reviews and actually produces better, more testable specs.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 1:11Quality and requirements
- 2:59Requirements types
- 4:24Functionality vs quality
- 5:27Stakeholder needs
- 7:15Requirements problems
- 8:42Testable requirements criteria
- 10:50Ambiguity and communication
- 13:37Transformation errors
- 16:29Generalization and deletion in requirements
- 18:15Nominalization and hidden processes
- 19:20Using templates
- 21:50Requirement templates
- 24:21Prototypes and links
- 25:28Tester mindset
- 26:53ISO syntax
- 28:58User stories and use cases
- 31:31Diagramming requirements
- 32:55Requirements tools
- 33:59Project deliverables
- 36:25Collaborative creation
- 38:55Breaking silos
- 40:01Reviewing requirements
- 40:43Collaborative quality assurance in Agile
- 41:06Summary
related talks
36mHow Testers Can Help Paving the Future of Modern Requirements Engineering
54mExtreme Shift Left / Out with the Requirement Engineer?
45mPanel Discussion | How to deal with bad requirements in testing?
34mHelping Testers Add Value to Agile Projects
44mExcellent Testing Starts With Excellent End-User Requirement Engineering and Specification
09m"The Tester’s Role: Balancing Technical Acumen and User Advocacy"
01h 02mAgile Testers and Test Managers: Now What?
01h 08mTesting Is Your Brand: Sell It!