ADS specializes in using Ruby on Rails to build advanced, scalable, database-backed web sites for organizations of all sizes. Find out more at our website.

When we work with a new customer to prepare an estimate we always ask for two things:

1. A list of who is going to be using the site (user roles)
2. What each of those people needs to be able to do

There are many reasons for approaching a requirements spec in such a way:

• For non-technical people this is an easy way to write requirements
• There is less work for the customer - they focus on the value they want to offer not how to make it happen (that’s our job)
• User stories can be created more easily
• The requirements are clearer so less back-and-forth is required
• Each bullet point can be easily tested by the customer during acceptance testing
• Long detailed specs make me nauseous and will most likely change many times over as the application is developed and deployed

How do you approach requirements gathering? What level of detail do you ask for when create an estimate?

Other posts you may enjoy

• When To Say NO To A Project
• There Is No Version 1
• Can Rails Affect Your Business’ Bottom Line?