What strategies do you use to review requirements in your projects?

MoT Content Discussions
,
1

Have a read of my new MoT article, “Finding software testing opportunities early with the Requirements Review Model.” This article walks you through how the model helps testers catch unclear, risky, or ambiguous requirements before they cause issues.

By using the Start, Spot, Turn, Apply approach, you can improve clarity, reduce assumptions, and collaborate better with your team.

RRM 690x388
RRM 690x3881920×1080 237 KB

After reading, let’s discuss:

  • What strategies do you use to review requirements in your projects?
  • What common pitfalls have you faced?
4 Likes
2

I take people first, artifacts second. By that I help to enhance a shared understanding of the problem and the proposed solution (or the solution space). I’m looking for anything people either find ambiguous or having different understandings of it.
In the direction of what needs to be developed as well what needs to be tested, guided by risks.

Pitfalls are for me mostly on social level. Some people don’t talk much at all, some can’t stay criticism, some say Yes to everything, I’m doing too specific jokes, games of power, etc. Bring any group dynamic you have in mind.

The team needs to have a good enough shared understanding. Any artifact is just a help to remember what we (tried to) agreed on.
Sometimes some short notes, not understandable for outsiders, are good enough.

2 Likes