Dec
14
BABOK 2.0 Update
December 14, 2006 |
The Body of Knowledge Team has been reviewing the feedback kindly provided by the Expert Advisory Group and working out how to integrate that feedback into the next release of the BABOK.
Our experts agreed that the work to date was solid, but identified three major areas for us to focus on when developing the next release.
- Version 1.6 of the BABOK can be construed as describing, or even requiring, a highly complex waterfall approach to business analysis. It needs to be adjusted to make it clearer how the tasks it describes apply in iterative, agile, and maintenance efforts.
- The BABOK, in its current form, frequently implicitly or explicitly assumes that the business analyst is involved in developing a software solution. We need to ensure that it is equally applicable to business process development.
- The current draft contains a lot of material that properly falls into the project management role–while a senior business analyst may perform project management tasks, the BABOK doesn’t need to describe them.
We also have a number of basic housekeeping measures to deal with, such as developing a standardized glossary of terms, copy editing the current content, and integrating material across chapters. The completion of the CBAP certification exam, launched this November, has also required that we institute a more rigorous change control process to ensure that Examination and Certification can determine if any changes to the BABOK impact questions on the certification exam.
Unfortunately, this has pushed back our hoped-for release date of late 2006. We are currently planning to release version 2.0 of the BABOK in March of 2007. As we approach that date, we’ll be preparing for a public review as well as a second round of review with our experts, and we will be putting out a call for volunteers to help us administer that process.
Thank you for your continued interest in the development of the Business Analysis Body of Knowledge!
This update also appeared in the IIBA’s latest newsletter. There’s also one minor piece of errata in that issue: the group pictured on page 2 is the Item Writing team and not the BOK Committee.
Comments
1 Comment so far
What I'm Reading- Communicating requirements to different stakeholdersBA Rocks!
- Product Management Reader: 13Nov08The Productologist
- Satisficing SprintsTyner Blain
- The Decline and Fall of AgileJames Shore
- Theory is Obsolete and other touchy topicsHerding Cats
- Agile Product Managers and Agile Product Owners Living Together in Harmonyenthiosys agile product management
- Rapid Results and the Big Systems ProjectProject X Discussions
- PMBOK, Agile and the need for TheoryHerding Cats
- A 5th element for the Agile ManifestoOn Product Management
- More on Agile Product Managers and Product OwnersScaling Software Agility
[...] I’m eagerly awaiting the release of the BABoK 2.0, it is tentatively scheduled to release in March of 2007. Kevin Brennan, over at Business Analyst Insight, has a post on the progress of version 2.0 and the three major areas of focus for this release: [...]