During a recent use case walk through session, I presented the UI mockup before we finished going through the whole use case. We ended up spending the whole session discussing the UI because people were so adamant on what they want on the UI they lost the big picture of what the use case is trying to accomplish. That said, my lesson learned is to walk through an entire use case first before showing any UI. This doesn't mean the approach of exposing UI early in requirement cycle is inappropriate, in fact, I preach religiously the benefit of having UI as supporting document to the use case. 1. UIs are so easy and quick to understand, they accelerate the requirement cycle. They help you to expose missing requirements or reach agreement with stakeholders early, thus save time and money on having to rework the requirements later. Personally, I'd rather find out any conflicts, issues early so I can form a plan to address them. 2. Stakeholders are involved early in design and help to ...
Comments
Post a Comment