SO I thought you had captured one of the Use Cases I would ask for. It's inherent in the name. Then after reading it I realized I had made an assumption which was not true, so I'll ask a different way.
How about a Requirements Inventory? Managing requirements for IT projects is... OMG awful. The DBs that are out there are hideous, limited in functionality and expensive. As a result, most companies are effectively tracking their requirements through email and excel spreadsheets. There must be a better, more intuitive way. Someplace that allows multiple people to work on it at the same time. Some way to track which business area came up with what requirement for what system which matches what High Level Requirement or Scope Statement.
I think as you manage your requirements for Querki, you will see what I mean.
Managing Requirements for a Managing Requirements Use Case will probably feel pretty "meta" and strange, actually.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2012-10-22 04:55 pm (UTC)How about a Requirements Inventory?
Managing requirements for IT projects is... OMG awful. The DBs that are out there are hideous, limited in functionality and expensive. As a result, most companies are effectively tracking their requirements through email and excel spreadsheets. There must be a better, more intuitive way. Someplace that allows multiple people to work on it at the same time. Some way to track which business area came up with what requirement for what system which matches what High Level Requirement or Scope Statement.
I think as you manage your requirements for Querki, you will see what I mean.
Managing Requirements for a Managing Requirements Use Case will probably feel pretty "meta" and strange, actually.