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