Sanity checks for feature lists
Cutting Through - Sanity checks for feature lists:
Here’s a simple technique that we use on a regular basis as a ’sanity check’ for the technical requirements of a development project.
- If it’s not already been done, write out the functional specifications as a numbered list of requirements.
- Do the same for the business requirements that were identified in the earlier stages of the project.
- Take each functional requirement in turn and cross-reference it against one or more business requirement. At each iteration, ask yourself “what business benefit does this feature deliver?”
- If there are any functional requirements that can’t be linked to a business requirement, ask yourself if it’s needed - and be very sceptical of the answer if it’s “yes".
Comments
No comments yet.
RSS feed for comments on this post.
Leave a comment
Sorry, the comment form is closed at this time.