Too many companies don’t document their requirements.
Worse still, too many companies over-document their requirements.


topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2005%2F12%2F27%2Fmanaging-requirements-conversations%2F”, “style”: “big”, “title”: “Managing requirements conversations” }); 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 [...]

topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2005%2F12%2F22%2Fcommunicating-a-delivery-schedule-with-use-cases%2F”, “style”: “big”, “title”: “Communicating a delivery schedule with use cases” }); Use cases are a great tool for establishing the scope of a project. They provide a framework for defining what needs to be implemented (if it doesn’t support a use case, we don’t need to implement it). They also set expectations [...]

topsyWidgetPreload({ “url”: “http%3A%2F%2Ftynerblain.com%2Fblog%2F2005%2F12%2F07%2Fconsolodation-in-the-rm-software-space%2F”, “style”: “big”, “title”: “Consolodation in the RM Software space?” }); SteelTrace is targeted as a likely takeover candidate in this post from the Computer Business Review online. Borland (CaliberRM) and Teleologic (DOORS) are the most likely suitors identified in the article.