Anyone know any good resources for learning/teaching how to do requirements reviews… what kind of things to look for? Seems to be plenty on “how to run a requirement review process” but not really how to train people to be good at it. Like… make sure its testable, make sure you can understand what i…

By content: I suggest to empathize with the user and imagine the future use of the function. What problem has the user and how we intend to help him. Especial testers should imagine what potential problems can occur, which will keep the user from solving his problem. By process: An important po…

Not so much a specific training tool yet the Feature Chat Sheet provides a good set of prompts for people to try out and get good at requirements reviews.

I cannot not add 6 thinking hats as a trick to have up your sleeve . Six Thinking Hats - Wikipedia . Uncovers loads of assumptions, but requires that 3 or more people are writing the requirements down for the requirements to really be something a team can implement. To be fair I’ve worked in very f…

I am creating a 5 part blog series on this topic. This is part I: Requirement Gathering Blog Series, Part 1: Understanding Requirements - The Test Tribe

As well as the excellent things people have already suggested, I find it helpful to think about users, data and interfaces with other code. Think through the different kinds of user (personas, if you have them). How will each kind of user interact with the change? Will things get better/worse/diffe…

Here is a tip from the forum: [image] Isn't HTSM equally applicable when creating requirements? 🙋 Questions This is a philosophy of testing type question. James Bach’s HTSM is a powerful model for testers. Can’t the same categories be used when creating requirements? Gi…

I do exactly this, plus a checklist of ideas more specific to the risks (including previous problems) of the team.

Being good at evaluating software in context is a lifetime skill, so it’s difficult to provide a quick answer. That’s one of the benefits of having a skilled tester. The first tip is to practice. Documented requirements are often bad, hard to interpret, requires domain understanding, incorrect, con…

Finally documents, which contain requirements, are just artifacts of communication. What matters is that everyone understands good enough the problem to solve, the solution to implement and the work to do. Do not concentrate to much on documents. What matters is who wants to communicate with you b…

You can partially automate requirements reviews with ScopeMaster (AI requirements analyser). It also auto-generates test scenarios instantly from the requirements, that are fully traceable back to the requirements. (Nb, I work for ScopeMaster)

Learn to do requirement review better

Discussions

sebastian_solidwork (Sebastian Stautz) 21 March 2023 17:49 7

Here is a tip from the forum:

Topic		Replies	Views
How do you go about reviewing a large set of requirements? MoT Content Discussions bias , requirements , critical-thinking , analysis , shift-left	1	473	29 May 2023
What strategies do you use to review requirements in your projects? MoT Content Discussions risks , requirements	1	110	23 April 2025
How do you usually approach testing when the requirements are vague or incomplete? Discussions learning , process , career-development	31	876	14 May 2025
Testing Against Implicit Requirements with Nicola Lindgren 🪐 TestBash collaboration , testbash-home , requirements	3	724	18 June 2021
Principle 5 - Exercise 1: Can you learn more from requirements? Discussions modern-testing-intro	1	73	8 May 2026

Learn to do requirement review better

Related topics