Managing Requirements Conversations 2005/12/27
In Documents vs. Conversations, on the Pyre blog, Greg Wilson does that thing that we so rarely do – he takes a step back, and thinks from an entirely different perspective about managing requirements. He proposes the idea of managing requirements as conversations, instead of as documents.[…]
Why We Should Invest in Requirements Management 2005/12/28
Need to convince someone in your management chain why they should invest in managing requirements? There are some great arguments in this post by sudhakar -[…]
CRUDdy Use Cases And Shakespear 2005/12/29
CRUD (Create, Retrieve, Update, Delete) is an acronym used to refer to a set of mundane, important, and indirect (if not implicit) requirements or use cases. To create a report on orders, you have to first create the orders and retrieve them. Further, the ability to update (edit) and delete the orders is probably also important. Another description of the CRUD pattern is here.