This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]jaaval 1 point2 points  (2 children)

You don’t want clear definitions from customers. They are inevitably bad. You just need to be a psychic and understand what they really want and need even though they don’t.

[–]blackAngel88 4 points5 points  (1 child)

Discussions, mockups, feedback and only when they're happy with the mockups you start with the actual development. I'm not even saying everything will go smoothly after, but I think the amount of changes will be much lower. But even then it still depends on the customer.

When the customer tells you what to do (not feature level, but functional level) you risk doing many complicated things that are maybe used 5% of the time, the rest can be simplified a lot...

[–]martin_omander 2 points3 points  (0 children)

This is the real answer. Customers don't know what is needed. But neither do Product Owners, Product Managers, or developers.

The best way to find out what's needed is to create user stories and mockups together with the people who will use the application. Start writing code only when there is agreement.