In this blog post, Adrian McGrath discusses how a ‘Model Office’ approach to requirements capture, design, build and test can play a significant role in improving the success of an Electronic Document and Records Management System implementation.
Using a Model Office to Gather Requirements
In this blog post, James Christie starts from the fact that perfect requirements don’t exist to discuss the idea that the quality of requirements is directly influenced by the time and money you invest in crafting them.Read More
In this blog post, By Scott Sehlhorst starts with a simple fact: if there is a lot of discussions on how to write requirements, there is not so much material on why to write requirements. His advice is that you should start by thinking about why you write requirements before you decide how to write […]Read More