Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

BABOK - Business Analysis Body of Knowledge presentation - May 2013

A short presentation on BABOK - Business Analysis Body of Knowledge and BA skills and techniques
by

Cristian Leon

on 16 July 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of BABOK - Business Analysis Body of Knowledge presentation - May 2013

Business Analysis
Body of Knowledge
(BABOK) walkthrough BABOK represents a collection of activities and techniques that make up Business Analysis. It is the stuff that we Business Analysts do on a daily basis.

In general terms, BABOK guide reflects generally accepted practice in the field of Business Analysis (BA)

BABOK describes Business Analysis areas of knowledge, associated activities and the skills necessary to be effective What is Business Analysis Body of Knowledge (BABOK) It is not a methodology or a specified process

It is not a “how to do business analysis” resource guide

It does not prescribe or favor a specific methodology

BABOK tells you “What to do in” but not “How to do” Business Analysis What Business Analysis Body of Knowledge (BABOK)
is NOT Elicitation = the practice of collecting the requirements of a system from stakeholders.

Elicitation methods used:
brainstorming
observation
meetings
interviews
focus groups
documents analysis Business needs - Identify and define why a change to organizational systems or capabilities is required

Solution scope - which new capabilities a project or iteration will deliver

Business case - determine if an organization can justify the investment to deliver a proposed solution.

Requirements management plan - used to approve requirements for implementation and manage changes

Stakeholders' map
identify which entities are directly involved or affected by the new system or solution Requirements Elicitation Inputs



an informal statement of a requirement

Type: As a <role>, I want <goal/desire>

Eg.: “As a user, I want to search for my customers by their first and last names.” Requirements Management and Communication - I Requirements Management and Communication - II
The goal of tracing is to ensure that requirements are linked back to a business objective.
Tracing requirements also includes change management, requirements allocation (assigning requirements to solution components) and impact analysis.

Impact analysis is created by the Business Analyst and when a requirement is changed, the impact of the change can be assessed throughout the project. Analytical Thinking Creative thinking Problem solving Systems thinking Personal Characteristics Ethics Personal organization Trustworthiness Business Knowledge Business practices Industry knowledge Organization knowledge Solution knowledge Communication Skills Oral communication Teaching Written communication Interaction Skills Facilitation Teamwork Negotiation Requirements Management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements.

In this process you control and communicate changes to relevant stakeholders

Inputs:
Solution scope - which new capabilities a project or iteration will deliver
Requirements Management Plan - this plan defines the process to be followed in managing requirements.
BA Comm Plan: determines how best to receive, distribute, update and escalate information with stakeholders. Functional decomposition technique breakdown process Decomposing a problem without fully understanding the relationship between pieces may create an inappropriate structure. Interface Analysis Identify interfaces between solutions and components and describe how they will interact
user interfaces
external application interfaces
external hardware devices interfaces Specification of the interfaces should prevent difficulties in integrating multiple components. Non - functional requirements Business Analysis Skills Describes the qualities of a system.
Categories:

Reliability
Performance
Operability User Story THE END Business Analysis Techniques Business Analysis Skills Business Analysis Management & Communication Business Analysis Requirements Elicitation Business Analysis Planning & Monitoring - I Business Analysis Planning & Monitoring - II
identification of stakeholders
selection of business analysis techniques
selection of a process to manage requirements
selection of a method to trace the progress 1. Identify the approach that suits your project.
Plan driven approach:
Incremental model (the project is released with the last increment) or Waterfall model
Change driven approach (Agile): Scrum or Extreme Programming (XP - programming in pairs)

2. Write an initial list of High Level Requirements based on inputs from project's stakeholders

3. Create a RACI matrix – Responsible Accountable Consulted Informed

4. Implement a business process improvement methodology.
Six Sigma (99.99966% free of defects - used in industries)
Capability Maturity Model Integration for IT industry Business Analysis Planning & Monitoring Requirements elicitation Which stakeholders can you identify in your project? Domain SME Customer Sponsor Business Analyst Operational support Project Manager Development Team End-user Implement. SME Supplier Requirements Traceability Which activities are necessary in order to complete a business analysis effort: One or more sentences in everyday or business language of the end user or customer that captures what a user does or needs to do, defining the functions a business system must provide
Security
Compatibility
Maintainability
Transferability
Full transcript