home

Kevin Brennan's blog

BABOK version 2 Public Review Underway

The IIBA is pleased to announce that the draft of version 2 of the Guide to the Business Analysis Body of Knowledge® (BABOK®) is now available on the IIBA website for public review. This revision represents over two years of work by IIBA volunteers and incorporates the results of an expert review and the results of the first set of practitioner reviews.

We invite you and all other practitioners of business analysis, whether or not they are members of the IIBA, to download the draft text from our website and provide us with feedback on the quality and relevance of this material. Instructions on how to provide this feedback can be found on the BABOK version 2 page or in the Introduction of BABOK version 2. The draft text will remain available until May 15, 2008.

Solution Assessment and Validation KA

The "1.7" draft of the Solution Assessment and Validation KA is now available for download by IIBA members.

This content was completed after the creation of the CBAP exam and was not designed using the exam content as a reference. If you are studying for the exam you should continue to use version 1.6 as the basis for your study.

A Preview of BABOK v2

We know people have been waiting eagerly for the release of version 2.0 of the BABOK.

In June, a few of us gathered in Hartford, CT to integrate the BABOK. The team took all of the information we’ve gathered, including the feedback from our expert and practitioner reviewers, and evaluated the structure of each of the knowledge areas. We worked to define how each of the KAs fits into the larger picture of business analysis. The goal was to define the BABOK in terms of the “essentials” of business analysis. We also had to ensure that each KA was coherent, complete, and that it contained enough tasks to be a psychometrically cohesive unit for the purposes of certification.

    Sponsored Announcements & Special Offers

view counter

Whitepaper from HP - Why Focus on Requirements Definition Management in the Application Lifecycle?

Increasingly, smart businesses are looking much closer at requirements definition (RD) and requirements management (RM) (sometimes grouped together under the Gartner-coined phrase, requirements definition management (RDM)) to streamline the entire application lifecycle. Why? Because systematic and effective RDM captures software defects earlier in the lifecycle, and it reduces the overall likelihood that defects will be introduced. That’s important. How important? According to one study, the cost to fix a defect after delivery is more than 100 times the cost to fix it in the requirement and design phase. No business wants to be hit with that bill. Now to add to this the growing interest in agile development techniques as a way to deliver higher quality applications and we have an interesting recipe for success.

Download a Free Copy

view counter
© 2007-2010 Requirements Networking Group All rights reserved. contact | advertise | privacy
Requirements Networking Group