Developers keep telling me there is not enough detail in the requirements spec!

Developers keep telling me there is not enough detail in the requirements spec! …or they are having a hard time understanding the requirements

problem

  • BAs might say…
    • Developers seem to want every last detail defined…can’t they think for themselves.
    • Or they just make a lot of assumptions. That are clearly wrong! ¬†what were they thinking?
  • Developers might say…
    • The requirements are not clear…there are so many details that are left out.
    • It is difficult to see the big picture and overall flow from a user perspective

potential reasons for this

  • the spec document is not very clear or well organized
  • the spec document was written in a form that was easy to create…instead of easy to understand…
    • for example if you write requirements just as a collection of statements that are “traced or linked to each other”, this can be hard for a developer to consume and understand.
  • you rely on the developer to read the spec and understand it

solutions

  • walk through the requirements with the developer
  • get the developer involved early and often in the review of the requirements
  • make sure the requirements are written in a form that is easy to understand – e.g. from a user point of view such as use cases, storyboards etc.
  • don’t duplicate requirements, as they can get out of sync and confuse the team.
  • ensure your requirements don’t conflict each other

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>