The traditional ways that we describe how to build something, whether it's a blueprint for an office building or the specification for a computer program, it always involves a document that describes WHAT to build and often includes information on HOW to build it.
However, these documents are often missing critical information on WHY these features are wanted in the first place and WHO they are for. Both of these pieces of information tell us a lot about what to build and knowing them we can often build better features for our users then was originally conceived.
from DZone.com Feed http://bit.ly/2MP0ZRT
No comments:
Post a Comment