2 February 2008

Carnival of Business Analysts #6: Requirements Communication

Welcome to another edition of the Carnival of Business Analysts. Regular readers know we are tracking through the knowledge areas of the BA BOK (version 1.6.) The Carnival of Business Analysts seeks out blog posts on the topic of business analysis.

Each month I have nominated a theme and then hunted down posts related to that theme. I am assisted by a handful of bloggers who nominate posts they have written or read, and together we construct this digest of thinking on the edition's monthly theme.

In the first 5 editions we have covered Requirements Planning, Requirements Elicitation, Requirements Analysis, The BA and Quality and the nature of the Business Analyst Role. (You can see the whole list here.)

This is edition #6 and it focuses on Requirements Communication.

To start with, read a quick definition or Requirements Communications from the BA Handbook on the knowledge area.

Then, to reinforce that communications is an important and troubled part of requirements management read what Mike has to say about communication at Leading Answers in “We Don’t Want User Input” Angie at B2T also asks When you communicate is anyone listening? And following on from this there is a post at Seilevel titled “I’m not going to read your requirements.

So you can see there is a challenge in managing people’s communications bandwidth.

Looking more broadly, are there lessons we can learn from other industries? Nada Serajnik has written a post called Can We Learn From A Public Communication Campaign? And Cinda Voegtli tells us What the Girl Scouts Could Teach Us About Project Communication.

Dave Bouman sums it up with the though that regardless of how you manage your software development, at the end of the day “It's all about Communication...

So how do we manage requirements communication? James Brausch has put forward a model that may be useful in Four Types Of Systems

Lastly Fred W Black reminds us that “Honesty” is a fundamental to good communication.

This edtion is a bit shorter than usual. I have been busy and so haven’t had the time to search as deeply as usual for content. If anyone has something they’d like to add, please do so in the comments.

That concludes this edition. Submit your blog article to the next edition of the Carnival of business analysts using our carnival submission form. Past posts and future hosts can be found on our blog carnival index page.

Next edition will be published 10th March and will be themed on Solution Assessment and Validation.

No comments:

Post a Comment