We all might fall into a situation where a business requirement is not clear. Some people will assume a point or two, some seek clarification from business.
When was the last time assuming something about a story caused more trouble than adding speed to development or whatever you "assumed" would happen?
Discuss!
Top comments (4)
I just started a new gig, and while I ask a lot of questions, to hit the ground running i’ll have to make a number of assumptions while I’m learning both the domain and codebase. Some of those assumptions will turn out wrong, but that’s part of the learning process. Over time as I build expertise in the business and process i’ll make less assumptions and the assumptions I do make will be wrong at a lessened frequency.
Totally relatable, but I was looking for examples to show people how they can hurt more than help sometimes
It happened that the business requirements were vague and I burned myself to come with something 100% perfect. After all the stress I've gone through, it turned out that their requirements is basic and my extra effort wasn't needed. I'm now between asking for clarifications and details or achieving the minimum possible until they ask for more?
Totally get what you said, nowadays, I always ask for clarification even for minimum if I don't have them and never assume anything. Unless you're a business expert and know some basics around roadmap of the product, always ask