Why, oh why do BAs make up their own requirements? Stakeholders generally have a pretty good idea og things they want already without you piping up about new functional requirements that are unrelated to any stated user, or even business, requirements.
I've been in so many situation where the user's justification for an enhancement is "The BA suggested it, but we don't really understand why". This ends up costing tens of thousands of dollars to produce something no one needs - and all project methodologies are vulnerable to it as soon as the project team starts speaking for instead of with stakeholders.
The root cause is a muddled defintion of "Requirements", and a failure to apply the simple lesson that you have two ears and one mouth and they are to be be used in that proportion.
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment