Nobody seems to read my requirements spec document! &#*#!

  • why
    • too much volume
    • hard to follow
    • all the details are referenced to somewhere else
    • don’t know what it will look like
  • do it differently
    • describe from user point of view
      • user scenarios
      • user stories
      • use cases
      • storyboards
      • use case storyboards
    • de-normalize
      • don’t duplicate things….but combine them.
      • Combine your use cases, storyboards and wireframes into one deliverable
    • don’t duplicate the story flow
      • scenario, use case, storyboard and test cases all duplicate the same story flow…stop it
    • walk them through the requirements

Leave a reply

Your email address will not be published.

You may use these HTML tags and attributes:

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>