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

Slides:



Advertisements
Similar presentations
Enterprise Grants Management The Time is Right. Transformation From To.
Advertisements

Chapter 5 – Enterprise Analysis
Requirements Management & Communication Chapter 4
Alternate Software Development Methodologies
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Lecture 13 Revision IMS Systems Analysis and Design.
Software Requirements
Analysis Concepts and Principles
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Major Exam II Reschedule 5:30 – 7:30 pm in Tue Dec 5 th.
PPA Advisory Board Meeting, May 12, 2006 Assessment Summary.
SE 555 – Software Requirements & Specifications Introduction
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Software Engineering 1 Therese Hume X361 Room 7, prefab (mon,wed)
1 Lecture 6 The Systems Analyst (Role and activities) Systems Analysis & Design Academic Year 2008/9.
Chapter 8: Development of Business Intelligence
CBAP and BABOK Presented to the Albany Capital District Chapter of the IIBA February 3, 2009.
socio-organizational issues and stakeholder requirements
Kris Hicks-Green April 23, 2013 IIBA Austin
Are Business Analysts Enterprise Architects?
Lets test our understanding with sample questions from the chapter.
What is Business Analysis Planning & Monitoring?
Developing Enterprise Architecture
Continuation From Chapter From Chapter 1
BUSINESS ANALYSIS BUSINESS ANALYSIS Toolkit.html.
Software Project Management Introduction to Project Management.
Requirements Analysis
BSBPMG502A Manage Project Scope Manage Project Scope Project Scope Processes Part 1 Diploma of Project Management Qualification Code BSB51507 Unit.
Software System Engineering: A tutorial
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Establishing a Best Practice Community It Takes a Village to Make a Successful Project Presented by Emily Iem, PMP, CBAP.
Business Analysis and Essential Competencies
Instructore: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Requirement engineering.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 3 Project Management for Strategic Goal Achievement.
IIBA - Cedar Rapids Chapter Thursday, Sept. 22, 2011.
BMAN Integrative Team Project Week 2 Professor Linda A Macaulay.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Lecture 7: Requirements Engineering
1 Introduction to Software Engineering Lecture 1.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Copyright  2005 McGraw-Hill Australia Pty Ltd PPTs t/a Australian Human Resources Management by Jeremy Seward and Tim Dein Slides prepared by Michelle.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
1 Chapter 8 Building the Analysis Model (1) Analysis Concepts and Principles.
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
(c) Adaptive Processes Consulting Be with the Best!
Requirements Analysis
Requirements engineering The process of establishing the services that the customer requires from a system and the constraints under which it operates.
 CMMI  REQUIREMENT DEVELOPMENT  SPECIFIC AND GENERIC GOALS  SG1: Develop CUSTOMER Requirement  SG2: Develop Product Requirement  SG3: Analyze.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Outlines Overview Defining the Vision Through Business Requirements
UTA/ARRI. Enterprise Engineering for The Agile Enterprise Don Liles The University of Texas at Arlington.
Software Engineering Lecture 10: System Engineering.
Project Management Processes for a Project Chapter 3 PMBOK® Fourth Edition.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Building a BA Center of Excellence Gain Momentum...Produce Results!
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Information Technology Project Management, Seventh Edition.
1 Capstone design and curriculum renewal Margot McNeill Learning and Teaching Centre Thursday, 2 July 2009.
1 International Institute of Business Analysis Vision: The world's leading association for Business Analysis professionals” Mission: To develop and maintain.
true potential An Introduction to the First Line Manager Programme’s CMI Qualifications.
 System Requirement Specification and System Planning.
Scope Planning.
Chapter 5 – Requirements Engineering
Building a BA Center of Excellence
CV-1: Vision The overall vision for transformational endeavors, which provides a strategic context for the capabilities described and a high-level scope.
Business analysis Lecturer: Kotlik Andrey Valeriyevich
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Business Analysis and the Value of Requirements
Presentation transcript:

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

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

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”

2011 (R). For IIBA(R) and chapter use only Resources IIBA Web-site IIBA Community (groups, blogs, forums, library) Internet (Laura’s CBAP Journey) Linked In Output from this Study Group

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

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)

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

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

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.

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.

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

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?

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

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

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

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

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

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

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

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.

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

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

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.

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?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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