←back to thread

4 points souravpradhan | 1 comments | | HN request time: 0.202s | 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. t0duf0du ◴[] No.46287368[source]
Our manager comes every 3-4 months, and assigns a ticket. Literally the only TEXT in the whole damn ticket was `Auto discovery in host and k8s`.

Auto discovery of fucking what?!!!

He writes in the message "IMP: we have a month so lets try to push to stage/BETA in 2-3 week and test it for a week and make it live before end of month."