What’s your idea of what the IIBA BOK is?

 

book-809396_1280

What is the IIBA BOK?

After my last post, a lengthy discussion started in LinkedIn regarding what the IIBA BABOK is.

One commenter – Magnus Stensson – posted a superb comment…

I think there are, roughly speaking, three different groups of interpreters when it comes to BOK’s, be it BABOK, PMBOK, etc.

1. Those who see them for what they are. A collection of current best practices, tools, tips, methods, vocabulary, etc.. grouped into somewhat logical sections called knowledge areas. The reader can get tips and inspiration while choosing how to apply the information in there to suit the environment they are working in. This group has the best use of the BOK as they adapt it to reality and use it to enhance their knowledge and practical ability in the area.

2. Those who, because it is not prescriptive and describes everything in a How to manner, see it as fluffy, too theoretical and incomprehensible, and thus unusable. They are the ones who grumble about it being too theoretical and not useable in the real world.

3. The BOK evangelists who see it as the bible of all things in the area, They seek to apply all knowledge areas and techniques to all projects regardless of scope, creating massive documentation and inefficiency. Everything is referred to against the BOK. “We must do transition requirements as the BOK says so”. “we need these models because BABOk says so”,.. etc. (unfortunately I’ve worked with these people….) . This group refuses to adapt the BOK to suit the situation and end up destroying its reputation because their co-workers, who haven’t read it, see it as a theoretical source of impracticality.

He summed it up nicely.

Check this out:
10 Steps to Successful Requirements Gathering

Further to that, his parting shot was…

The views in discussions like this one reflect which group people subscribe to… ūüôā

 


Recommended Reading
(Important Disclosure)