Requirement specifications make more sense when you have a fixed project lifecycle. What you are describing sounds a lot like an iterative project life cycle and Agile project management is much better suited to it. In agile project management, requirements are managed as user stories. A user story is a simple way of describing a requirement in this format:
As a (role) I want (something) so that (benefit)
for example, for a shopping cart app, one user story can be:
As a registered user I want to add a listed product to the cart so that i can order it.
With each iteration, you can go back and see if you need to add a new user story or modify an existing one. For starters, you can keep user stories in a spreadsheet (one per row) but many other advanced agile pm packages are available both for online and offline use.
发布评论
评论（1）
当项目生命周期固定时，需求规范就更有意义。您所描述的听起来很像迭代项目生命周期，而敏捷项目管理更适合它。在敏捷项目管理中，需求作为用户故事进行管理。用户故事是一种以这种格式描述需求的简单方法：
例如，对于购物车应用程序，一个用户故事可以是：
每次迭代时，您都可以返回并查看是否需要添加新的用户故事或修改现有的用户故事。对于初学者来说，您可以将用户故事保存在电子表格中（每行一个），但许多其他高级敏捷项目管理包可供在线和离线使用。
Requirement specifications make more sense when you have a fixed project lifecycle. What you are describing sounds a lot like an iterative project life cycle and Agile project management is much better suited to it. In agile project management, requirements are managed as user stories. A user story is a simple way of describing a requirement in this format:
for example, for a shopping cart app, one user story can be:
With each iteration, you can go back and see if you need to add a new user story or modify an existing one. For starters, you can keep user stories in a spreadsheet (one per row) but many other advanced agile pm packages are available both for online and offline use.