Forums for the Business Analyst

 
  Modern Analyst Forums  ModernAnalyst.c...  Community & Por...  BABOK 2.0 Made Alot Easier To Understand
Previous Previous
 
Next Next
New Post 10/27/2009 5:24 PM
User is offline Tony Markos
493 posts
5th Level Poster


BABOK 2.0 Made Alot Easier To Understand 

To all:

I don't know why all the BABOK authors used something called input/output diagrams to basically provide the higher level organization for a large part of BABOK 2.O.    With that organization, coming up with a comprehensive, integrated understanding of the essential functions/tasks and their relationships is next to impossible.   If you try to data flow diagram out those input/output diagrams, it is very easy to see why!

However, when you properly data flow diagram out the BABOK 2.0 diagrams, then the BABOK is alot easier to understand.

Tony

 
New Post 11/5/2009 2:03 AM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: BABOK 2.0 Made Alot Easier To Understand 

Tony - the way I read it, the BABOK 2 is not an integrated approach to doing work.  It's a loose collection of non-integrated practices.

The problem a DFD presented fort his version of the BABOK would be the lack of 'one best way.'  THey wanted a toolkit that is flexible enough for several different contexts.

 
New Post 11/5/2009 3:22 PM
User is offline Tony Markos
493 posts
5th Level Poster


Re: BABOK 2.0 Made Alot Easier To Understand 

Craig:

Section 1.5.2 of the BABOK 2.0 states :  "Each task [on the diagrams] should be performed at least once during the vast majority of initiatives....."  Earlier, the handbook states that the given tasks are perfomed most of the time, tailored to specific conditions.    So typically, each task would  be done whether the project is, for example, Waterfall or Agile. 

Section 1.5.2 also states that [the diagrams are constructed to reflect that]: "Iterative or Agile lifecycles may require that tasks in all knowledge areas be performed in parallel, and lifecycles with clearly defined phases will still require tasks from multiple knowledge areas to be performed in every phase.".

 

The way I read it, the problem is not that one set of input/process/output diagrams does not capture the majority of situations (contexts), it is that the diagrams are not integrated input/process/output diagrams, making them very difficult to understand as the reader must do this integration in order to understand how things systematically flow .   

Tony 

 
Previous Previous
 
Next Next
  Modern Analyst Forums  ModernAnalyst.c...  Community & Por...  BABOK 2.0 Made Alot Easier To Understand

Community Blog - Latest Posts

Fabricio Laguna talks Business Analysis and AI
I recently connected with Fabricio Laguna, aka The Brazilian BA. Fabricio is a passionate and pioneering business analyst from Brazil. During our conversation, we had a thought-provoking discussion on how artificial intelligence stands to shape the field of business analysis in the years ahead. While AI promises to transform many aspects of busines...
Business Architecture, Ontology and More with Terry Roach
It's been a privilege meeting Terry Roach, a visionary in the field of enterprise architecture and business architecture. Terry's insights into the evolution of business models, the importance of ontology in architecture, and the potential of AI to shape our future were not only thought-provoking but also a reflection of his extensive exper...
Today I had the pleasure of chatting to Jignesh Jamnadas, Chief Operations Officer at Mosaic, about his Blueprints for Success. As a Senior Finance and Operations Executive, Jigs (as he is known to many) has a holistic understanding of all facets of business and a flair for managing both people and processes. Having worked with Jigs, I was struc...

 



Upcoming Live Webinars




 

Copyright 2006-2024 by Modern Analyst Media LLC