Don’t just ‘understand’ requirements – IRON OUT requirements !
Let me explain..
No one has a clear picture of exactly what we want to build, that is the reason we build iteratively.
Therefore while discussing requirements, engineers are mostly interested in – just tell us what to develop.
The approach instead has to be – let’s ‘brainstorm’ what to develop.
The product owner should have a decent picture of what they expect, but they’d lack technical insights
Plus they CANNOT know everything and most proably have not thought of all the risks / assumptions
It takes different engineers wearing different hats (Dev, test etc.) to point out assumptions & risks BEFORE we lock in what to develop..