1. BABOK ® v2.0 Study Group - Brisbane An Overview of the structure of the BABOK 2.0 James Brandt 1

2. Introduction  House keeping  Group Introduction  Expectations  Be prepared  Contribute  Have fun  Support each other

3. 2011 (R). For IIBA(R) and chapter use only PD Credits  PD Credits:  1:1 course hours for course participation (max 14)  Student attendance is taken for each session and is recorded to validate attendance  Students should complete each “Hands-On Exercise”

4. 2011 (R). For IIBA(R) and chapter use only Resources IIBA Web-site IIBA Community (groups, blogs, forums, library) Internet www.batimes.com www.modernanalyst.com www.bridging-the-gap.com (Laura’s CBAP Journey) www.thebamentor.com Linked In Output from this Study Group

5. 2011 (R). For IIBA(R) and chapter use only Brisbane Study Group

6. 2011 (R). For IIBA(R) and chapter use only Overview  Defining Business Analysis  Key Concepts  Relationships of the Knowledge Areas  Inputs and Outputs  Tasks (and States)  Underlying Competencies (soft skills)  Other sources of BA information  Assignment of K.A. tasks for presenting the following week  Techniques (participant ‘ownership’ of a technique)

7. 2011 (R). For IIBA(R) and chapter use only What is the BABOK®? A globally recognised standard for the practice of B.A. It is a framework that describes the business analysis tasks that must be performed in order to understand how a solution will deliver value It is not a methodology

8. 2011 (R). For IIBA(R) and chapter use only What is Business Analysis Business analysis is the set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies and operations of an organisation and recommend solutions that enable the organisation to achieve its goals

9. 2011 (R). For IIBA(R) and chapter use only Key Concepts Domains The ‘problem’ area undergoing analysis. Solutions A solution meets a business need by resolving a problem or allowing an organisation to take advantage of an opportunity.

10. 2011 (R). For IIBA(R) and chapter use only Key Concepts Requirement  A condition or capability needed by a stakeholder to solve a problem or achieve an objective.  A condition or capability that must be met or possessed by a solution or solution component to satisfy a contract, standard, specification or other formally imposed documents.  A documented representation of a condition or capability as specified above.

11. 2011 (R). For IIBA(R) and chapter use only Requirements Classification Scheme Requirement TypeFurther Defined in Business requirementsEnterprise Analysis Stakeholder requirementsRequirements Analysis Solution requirements:  Functional  Non Functional Requirements Analysis Transition requirementsSolution Assessment and Validation

12. 2011 (R). For IIBA(R) and chapter use only Knowledge Areas  7 knowledge areas – the BA needs to understand these  Each has tasks to be performed  In rapid succession, iteratively or simultaneously  Starting point & Finishing point?

13. 2011 (R). For IIBA(R) and chapter use only Knowledge Areas What are they?

14. 2011 (R). For IIBA(R) and chapter use only Relationships

15. 2011 (R). For IIBA(R) and chapter use only Tasks  Purpose  Description  Input Classification Requirements [State or States]  Elements  Techniques  Stakeholders  Output

16. 2011 (R). For IIBA(R) and chapter use only Inputs/Outputs

17. 2011 (R). For IIBA(R) and chapter use only Inputs/Outputs

18. 2011 (R). For IIBA(R) and chapter use only Inputs/Outputs

19. 2011 (R). For IIBA(R) and chapter use only Stakeholders

20. 2011 (R). For IIBA(R) and chapter use only Outputs  An output is a necessary result for the work described in a task  Outputs are created, transformed or change state as a result of the successful completion of a task.  Although a particular output is created and maintained by a single task, a task can have multiple outputs.  An output may be a deliverable or be a part of a larger deliverable.

21. 2011 (R). For IIBA(R) and chapter use only Test – Key Concepts

22. 2011 (R). For IIBA(R) and chapter use only Techniques Non-functional Requirements Analysis Observation Organisation Modelling Problem Tracking Process Modelling Prototyping Requirements Workshops Root Cause Scenarios and Use Cases Scope Modelling Sequence Diagram State Diagrams Structured Walkthrough Survey/Questionnaire SWOT Analysis User Stories Vendor Assessments Acceptance and Evaluation Criteria Benchmarking Brainstorming Business Rules Analysis Data Dictionary and Glossary Decision Analysis Document Analysis Interviews Estimation Focus Groups Functional Decomposition Interface Analysis Interviews Metrics and Key Performance Indicators

23. 2011 (R). For IIBA(R) and chapter use only Techniques Purpose  Defines what the technique is used for, and the circumstances under which it is most likely to be applicable. Description  Describes what the technique is and how it is used. Elements  Format and structure of this section is unique to each technique. The elements section describes key concepts needed to understand how to use the technique. Usage Considerations  Describes conditions under which the technique may be more or less effective.

24. 2011 (R). For IIBA(R) and chapter use only Underlying Competencies  Understand the range of fundamental behaviours, characteristics, knowledge and personal qualities that support the practice of business analysis.  8 questions in the exam  Basic B?

25. 2011 (R). For IIBA(R) and chapter use only Analytical Thinking and Problem Solving This task is organized around the following behaviours and characteristics  8.1.1 Creative Thinking  8.1.2 Decision Making  8.1.3 Learning  8.1.4 Problem Solving  8.1.5 Systems Thinking

26. 2011 (R). For IIBA(R) and chapter use only Visual Memory

27. 2011 (R). For IIBA(R) and chapter use only Systems Thinking Purpose  BA must understand interactions and patterns within context of the whole system Definition  Properties emerge from interaction of components  Examining components in isolation is not sufficient for understanding the whole system Whole system includes:  People  Interactions  External forces  Other

28. 2011 (R). For IIBA(R) and chapter use only Behavioural Characteristics  Ethics  Personal Organization  Trustworthiness

29. 2011 (R). For IIBA(R) and chapter use only Business Knowledge  Business Principles and Practices  Industry Knowledge  Organization Knowledge  Solution Knowledge

30. 2011 (R). For IIBA(R) and chapter use only Communication Skills  Oral Communications  Teaching  Written Communications  Solution Knowledge

31. 2011 (R). For IIBA(R) and chapter use only Interaction Skills  Facilitation and Negotiation  Leadership and Influencing  Teamwork

32. 2011 (R). For IIBA(R) and chapter use only Software Applications  General-Purpose Applications  Specialized Applications

33. 2011 (R). For IIBA(R) and chapter use only Underlying Competencies

34. 2011 (R). For IIBA(R) and chapter use only Underlying Competencies

35. 2011 (R). For IIBA(R) and chapter use only Test – Underlying Competencies

36. 2011 (R). For IIBA(R) and chapter use only Other sources of BA information  Agile Development  Business Intelligence  Business Process Management  Business Rules  Decision Analysis and Game Theory  Enterprise Architecture (including the Zachman Framework for Enterprise Architecture™ and TOGAF™)  Governance and Compliance Frameworks, including Sarbanes-Oxley, Basel II, and  others  IT Service Management (including ITIL®)  Lean and Six Sigma  Organizational Change Management  Project Management  Quality Management  Service Oriented Architecture  Software Engineering (particularly Requirements Engineering)  Software Process Improvement (including CMMI®)  Software Quality Assurance  Strategic Planning  Usability and User Experience Design

37. 2011 (R). For IIBA(R) and chapter use only Assigning Knowledge Area Tasks Sample Time line Oct 27 th – Enterprise Analysis November 3 rd – Elicititation November 10 th – Business Analysis Plan and Monitoring November 17 th – Requirements Mgmt and Comms November 24 th – Requirements Analysis December 1 st – Solution Assessment and Validation

38. 2011 (R). For IIBA(R) and chapter use only Guidelines TypeDescription MemoryDefinitions – be able to recognise the BABOK® definition List - identify a list of characteristics Sequence – know the order of tasks InterpretationInterpret and apply BABOK® tasks and techniques ScenarioDescribe a project related situation

39. 2011 (R). For IIBA(R) and chapter use only 39 The Exam BAP&M: 19.33% Elicitation: 14% RM&C: 16% EA: 15.33% RA: 19.33% SA&V: 16% Questions on the Techniques and on Underlying Competencies have been assigned to a relevant Knowledge Area Knowledge Area# questions General and Underlying Competencies8 Business Analysis Planning and Monitoring27 Elicitation20 Requirements Management and Communication23 Enterprise Analysis22 Requirements Analysis27 Solution Assessment23 Total150

40. 2011 (R). For IIBA(R) and chapter use only Questions