When it comes to defining requirements for a new piece of software I find that everyone (even people who aren't involved in the business) have unique and insightful perspectives on what is "really" required (or so they always claim) my method for capturing, prioritizing and disambiguating said offerings is to ask for requirements to be written down, in long form, with diagrams. This request is often followed by extended periods of tumbleweed, which helps get to the crux of things enormously..
No comments:
Post a Comment