Requirements management and the project compendium

Save for later

Favourite

Posted by APM on 10th Jul 2010

Steve Armstrong with the Open University presented to the Yorkshire and North Lincolnshire branch in April 2004 on requirements management and the project compendium.

Steve began the presentation by giving an introduction to visual issue mapping and used compendium as an integrative tool. He exchanged some ideas about the difference between construction and software projects.

Capturing requirements can often result in piles and piles of
documents. Steve asks the group - who actually reads all this? Graham Tagg in his book, The Management of Problem Solving (1973) stated ''The true output of the group is ideas. Paperwork is merely a traditional and highly inefficient vehicle for getting these ideas across''. This statement in some cases could still be accurate today.

Steve suggested that problem solving used to be foolproof, you defined the problem; gathered the data; analysed the data; formulated a solution and finally implemented it. Simple or is it?

Of course, it isn't that simple and Steve looked at some of the problems that can arise and how using compendium as a tool can help to simplify these issues.

Steve presented a functional presentation that created debate between the delegates on requirements management but also discussion on the usefulness of the compendium theory.

Slides from Steve's presentation are available to download below.

Comments on this site are moderated. Please allow up to 24 hours for your comment to be published on this site. Thank you for adding your comment.
{{comments.length}}CommentComments
{{item.AuthorName}}

{{item.AuthorName}} {{item.AuthorName}} says on {{item.DateFormattedString}}:

Share this page

Recommended blogs

Save for later

Favourite

Recommended news

Save for later

Favourite

Save for later

Favourite

Join APM

Sign up to the APM Newsletter.