Requirements review is more than can we test this?
I came across a scenario where the team were testing the requirements and all was fine — however, what was missing was looking at those requirements broader than can we test these?
In my opinion, a requirements review is more than can we test it. It is about analyisng the requirements and answering the question
does it make sense?
If it does not make sense, then this is where you can then make suggested improvements.
A simple example
For example, you have a new password feature and the requirements is for the password to be 5 characters long. Does it make sense?
No it does not because it will make the password easier to guess. A suggestion would be to make it more than 8 characters long to make it harder to guess / more secure.
Look at all Requirements
I have given a very simple example here. You can do this with all types of requirements and along with “does it make sense?” you can ask the question
What is missing here?
I have come across a few ocassions where there is a gap in a requirement, say for example, they forgot to consider a security aspect of user role permissions. You can then call this out as a gap in the requirement.
