Return to Question

Edit 2: in response to Adam Wuerl comment:

Edit 2: in response to Adam Wuerl comment:

The root cause is that I had to work with completely non-techie stakeholders who do not care about requirements. They have wishes and tend to change their mind several times a day. On the other hand the process of requirements gathering has has to be fast and accurate.

While I adapted to such constraints in general there is an issue that I did not manage to overcome – software. It seems that there is no such thing as “RQ management software for mere mortals”.

To summarize, I want something like Basecamp but targeted exclusively to requirements gathering process from regular people (read non-geeks).

Now, if you have an Excel or Word document you will face with another issues:

The root cause is that I had to work with completely non-techie stakeholders who do not care about requirements.

Another issue is a large volume of data. I had to organize info on dozens of small projects each month.

While I have adapted to the process in general there is an issue that I did not manage to overcome – software. It seems that there is no such thing as “RQ management software for mere mortals”.

To summarize, I want something like Basecamp but targeted exclusively to requirements gathering process from regular people.

If you have an Excel or Word document you will face with another issues:

Edit 2: in response to Adam Wuerl comment:

Currently, I am using Redmine for requirements management. I think that bug tracker is the closest approximation of ideal tool described above. The problems with bug trackers is that they are either non-customizable (to the degree I need) or too flexible (read complicated).

I asked this question in the LinkedIn Requirements Engineering group and of the members has recommended to use Trac.

Unless there is a simple RQ management system available, customized bug tracker would be a good choice.