December 15, 2006
Visual Client Requirements
Here’s a great visual way of documenting client requirements for new website projects by Todd Warfel. I’m going to try this on my next project!
Filed by matteo at 1:33 pm under Web Design, Software/Development
Mark,
I am Todd’s business partner at Messagefirst, and I have to say the grid works rather well in getting everyone within the project to understand what is in scope and what is out of scope. It also helps with a rudimentary project roadmap. Todd and I have used it on a variety of projects and it keeps us from having numerous requirements review meetings as people are more likely to get what is in the project with the Task Analysis grid than from a 60 page requirements document. Please let us know how it works for you on your next project!
-bill
Thanks for the reply, Bill. As a software engineer for over 20 years, I have seen (and written) my share of requirements documents. And I think, as a rule, that once the document gets longer than about 10 to 20 pages, many clients won’t even read them! I think your visual approach is great. It sure makes sense to me!
Matt,
I’d be interested in seeing how you approach the conversion to technical requirements. I’m currently trying to modify a technical specfication document to make sense within this grid layout.
Sean,
I’m starting work on a project now that I’m going to use visual requirements on. I’ll post about it when the project is rolling.
Matt,
I’m doing the same , i’m working on a flash sitelet and i’ve gone and modified the grid to now have the following rows.
- Page / Screen
- Assumptions
- Navigation
- Tracking (custom for our needs)
- Functionality
- Technical Considerations
So far so good.