←back to thread

4 points souravpradhan | 1 comments | | HN request time: 0.195s | source

Every other day I face challenges while gathering requirements from various clients.

1. When everything becomes priority number 1 2. When the stakeholder goes back on the discussed requirements 3. Requirements change after every single meeting 4. During UAT a new stakeholder appears out of nowhere and says "This is not what we wanted" 5.You rely on SME for inputs who actually doesn't have a clue 6. Two clients from same team give you opposite requirements 7. Scope creep is the new fashion 8. THE BIGGEST OF ALL - The client doesn't know what they want

How do you navigate the horrors of the requirement gathering process to make yourself a better product manager?

1. AlanClifford ◴[] No.46262840[source]
“If you don’t get the requirements right, it doesn’t matter how well you execute the rest of the project.”—Karl Wiegers, Ten Cosmic Truths About Software Requirements

Every word Karl writes is gold. That man knows more about Requirements Engineering than anyone and has made a career of helping Requirements Engineers become better.