17 January 2008

Business Analyst BOKs

Posted by Craig
Did you know that there are several documents that are described as Bodies of Knowledge that business analysts should be aware of.

In alphabetical order:
  • BABOK - Business Analysts Body of Knowledge, by the IIBA
  • G2SEBoK - Guide to the Systems Engineering Body of Knowledge, by INCOSE
  • NPDBOK - New Product Developmet Body of Knowledge, by NPD Solutions
  • SWEBOK - Software Engineer's Body of Knowledge, by IEEE Computer Society
(Thanks Barbara for making me aware of the G2SE.)
And of course there are the Project Management BOKs which have a wider profile, especially the PMI one.
Lastly Kerber has offerred up a draft version of an Enterprise Architecture BOK.
He has also asked the very good question "How do we keep up with all this knowledge?" Apart from being a blogging and project geek, are there any suggestions out there?

Update 17 Jan 09:  Loretta Smith writes an article for ModernAnalyst on the DMBOK - the Data Modelling Body of Knowledge.






Picture originally publised hereby Rafael Lopes
Labels:

4 comments:

  1. Those two BoKs are calling my attention as a BA too:

    - Usability Bok
    http://www.usabilitybok.org/

    - EABOK: The Guide to the Enterprise Architecture Body of Knowledge
    http://www.mitre.org/work/tech_papers/tech_papers_04/04_0104/index.html

    I´ll eventually read them all, but how do we organize all that information in order to be better professionals?

    To consider everything at the same time is beyond the capabilities of the average brain (mine for example), so I believe we should choose some to pay more attention too.

    Any suggestion about who should we pay more attention in order to become better BAs?
    ReplyDelete
  2. Yes, So much reading to do! Maybe an information archiect could help us out by sorting through it all.

    I'll put my money on the IIBA's BABOK. Not becasue it is the best, but because it looks like it will grow to bethe most influential.

    Thanks for the extra link. I'll add it to the main post.
    ReplyDelete
  3. Hi, my name is Rafael Lopes, everything fine?
    Well, I see that the picture you used in this post is mine :)
    http://www.flickr.com/photos/bobeirasa/956242230/

    Can you please put the link to my flickr on it? I would apreciate.
    Thank you for your cooperation.

    :)
    ReplyDelete
  4. Thanks Rafael. Sorry I missed the original credit.
    ReplyDelete

Subscribe to: Post Comments (Atom)

Popular Posts

  • What is Project Scope? What should it be?
    I have been having a bit of a discussion over at the IIBA blog with Kevin (VP BOK) and Julian (Chief architect.) It’s migrated over to ...
  • User Story Template
    Due to popular demand I have aggregated some information on User Stories and created a simple template.  If you feel this would be useful to...
  • Change Request template
    Better Projects Templates I am uploading a couple of project document templates to Google Docs. As I add more I'll post them up here. You...
  • BCS forum on "Making Projects Work"
    You've heard many reasons why project fail.  Here is a discussion hosted by BCS on why projects work. The discussion covers four dimensio...
  • PDMs - Precedence Diagram Method
    The Precedence Diagramming Method ( PDM ) was developed in the early 1960s by H.B. Zachry in cooperation with IBM. It has largely repla...
  • Snowbird; Agile 2011 discussion on the BA
    In the below video some of the #10yrsagile participants discuss the role of the Business Analyst. A question for you; Do you agree or di...
  • Email, Whiteboards and Well-Caffeinated Wits
    This is a guest post by Jeff Hobbs.  Jeff is a project manager at ActiveState Software who provide pm and collaboration software. Email, ...
  • 7 Requirements Analysis techniques
    In one of the Carnivals of Business Analysts the theme was “ Requirements Analysis ." I searched the web far and wide and came up with a n...
  • An Introduction to Stakeholder Management
    The definition of a stakeholder is controversial. For example, project team members are generally not considered stakeholders, but in virtua...
  • The V-Model: Table of Contents
    I have written about the V-Model across several posts. The V model is a testing focused expansion of the software development lifecycle. In ...