Chapter 1: Possess a Clear Understanding of Business Analysis Seven Steps to Mastering Business Analysis (Barbara Carkenord, 2008)

Slides:



Advertisements
Similar presentations
Chapter 5 – Enterprise Analysis
Advertisements

© 2012 Autodesk BIM Collaboration Siva Koppula Technical Consultant.
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall 2-1 The Organizational Context: Strategy, Structure, and Culture Chapter 2.
1 Chapter 4 The Software Team Requisite’s 6 team skills for effective requirements management.
Chapter 8 Information Systems Development & Acquisition
Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Chapter 4: Beginning the Analysis: Investigating System Requirements
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
COMP8130 and 4130Adrian Marshall 8130 and 4130 Test Management Adrian Marshall.
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
CBAP and BABOK Presented to the Albany Capital District Chapter of the IIBA February 3, 2009.
project management office(PMO)
Bite sized training sessions: Business And Functional Requirements.
PMBOK – BABOK Which came first…the chicken or the egg? Do we really need both? November 2008 Errol Thomas MCSE, CEA, PMP, CBAP.
1 College of Engineering and Computer Science Computer Science Department CSC 131 Computer Software Engineering Fall 2006 Lecture # 2 Chapter 6 & 7 System.
Are Business Analysts Enterprise Architects?
Chapter 4: Beginning the Analysis: Investigating System Requirements
The Software Development Cycle Defining and understanding the problem.
Scrum Fundamentals: Analyst to ‘Agilist’ By Louis Molnar (C) IAG Consulting 2009 The Agile Business Analyst By: Louis Molnar.
BIS310: Structured Analysis and Design Introduction and Systems Planning Week 1.
S/W Project Management
1 Our Expertise and Commitment – Driving your Success An Introduction to Transformation Offering November 18, 2013 Offices in Boston, New York and Northern.
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
Requirements Analysis
1 IBM Software Group ® Mastering Requirements Management with Use Cases Module 4: Analyze the Problem.
LECTURE 1 What does a Business Analyst do? IFS 231 Business Analysis.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
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
The Challenge of IT-Business Alignment
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
IIBA - Cedar Rapids Chapter Thursday, Sept. 22, 2011.
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.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
1 4 Systems Analysis and Design in a Changing World, 2 nd Edition, Satzinger, Jackson, & Burd Chapter 4 Beginning the Analysis: Investigating System Requirements.
1 Activities covered by project management Feasibility study Is project technically feasible and worthwhile from a business point of view? Planning Only.
CIS 499 Senior Seminar Introduction to IT project management.
The views expressed in this presentation do not necessarily reflect those of the Federal Reserve Bank of New York or the Federal Reserve System Association.
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?
Software Requirements and Design Khalid Ishaq
(c) Adaptive Processes Consulting Be with the Best!
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
Generic competencesDescription of the Competence Learning Competence The student  possesses the capability to evaluate and develop one’s own competences.
IFS310: Module 2 1/18/2007 Systems Planning and SDLC.
IS Security Policies and Strategies Dr Gurpreet Dhillon Virginia Commonwealth University.
F O C U SQ U A L I T YE X P E R I E N C E Why Does a Project Need a Project Manager and a Business Analyst? Similarities, Differences and How They Work.
BABOK ® v2.0 Study Group - Brisbane An Overview of the structure of the BABOK 2.0 James Brandt 1.
Building a BA Center of Excellence Gain Momentum...Produce Results!
LOGO Business Analysis and IT Business Analyst An Introduction.
Shared Services Initiative Summary of Findings and Next Steps.
Enterprise Architectures Course Code : CPIS-352 King Abdul Aziz University, Jeddah Saudi Arabia.
Beyond the BACoE: Developing Business Analysis Maturity.
 System Requirement Specification and System Planning.
Project Planning: Scope and the Work Breakdown Structure
Identify the Risk of Not Doing BA
Building a BA Center of Excellence
Business analysis Lecturer: Kotlik Andrey Valeriyevich
Wear BA Hat for more Empathy -Sanchari Mitra, CCBA®
Beyond the BACoE: Developing Business Analysis Maturity.
How does a Requirements Package Vary from Project to Project?
THE BUSINESS ANALYSIS PROCESS MODEL
CHAPTER 9 (part a) BASIC INFORMATION SYSTEMS CONCEPTS
Presentation transcript:

Chapter 1: Possess a Clear Understanding of Business Analysis Seven Steps to Mastering Business Analysis (Barbara Carkenord, 2008)

What is Business Analysis IIBA definition: the set of tasks & techniques used to work as a liaison among stakeholders in order to understand the structure, policies and operations of an organization and recommend solutions that enable the organization to achieve its goals (identify business needs/problems and propose solutions)

What is Business Analysis

Business Analysis involves Identification of business problems/opportunities Elicitation of needs and constraints from stakeholders Analysis of stakeholder needs to define requirements for a solution Assessment and validation of potential and actual solutions Management of the “product” or requirements scope

You like technology, but not so much that you want to do it all the time. You like solving problems You like working with people and understanding their needs and concerns You get bored easily doing the same thing over and over Inefficiency and lack of effectiveness annoy you And… Why would you want to be a Business Analyst

TitleExperienceTasks Junior Business Analyst 0-2 years; may have business experience or IT development experience Elicit and document requirements for small, well- defined projects, often changes to existing systems. Ideally works with a BA mentor Business Analyst 2-5 yearsElicit, analyze, and document requirements for medium to large projects. Works with the project manager to scope new projects Lead or Senior Business Analyst 5-10 yearsElicit, analyze, and document requirements for large, complex, mission-critical projects. Supervises/mentors junior Bas. Works with the business to initiate and define new projects. Business Consultant/Clie nt Relationship Manager 10+ yearsAssist the business with strategic planning, business case development, and new product implementations. Helps to identify projects. Sets up and manages a business analyst center of excellence $89,000 $77,000 $48,000 Average salaries from Indeed.com Career Path

Would you make a good business analyst? –Turn to page 16 of your book –Answer the questions in your head, counting how many statements describe you –We’ll take a look at the distribution for the class Question

Business Analysis ……. Systems Analysis Former focuses on business solutions rather than technology solutions Help businesses design procedures, structures and technology to enhance the work Looks at how business models talk to the technology

Traits of a Business Analyst People skills Systems skills Business skills BA bridges the gap between people with differing levels of technical knowledge and business expertise (SMEs)

Overall responsibilities of BA gathers requirements from the client from the business point of view analyses these requirements and drafts a document (requirements definition) doc) writes use cases from that document for the technical people to understand

Key Terms / Concepts Requirement Project Product Solution Deliverable System / Software

Requirement –“Condition or capability required by a stakeholder to solve a problem/achieve an objective” (BABOK) –Core Requirement Components (data, processes, people) Data (Attributes Entities) Processes (or Use Cases) External Agents (or Actors) Business Rules