Business Analysis for Practitioners - Introduction

Transcription

1 Business Analysis for Practitioners - Introduction

2 COURSE STRUCTURE Introduction to Business Analysis Module 1 Needs Assessment Module 2 Business Analysis Planning Module 3 Requirements Elicitation and Analysis Module 4 Traceability and Monitoring Module 5 Solution Evaluation Module 6

3 COURSE OBJECTIVE At the end of this course, you will understand what business analysis is all about, why it is essential to the success of any project and how to perform it on your projects...

4 Business Analysis for Practitioners MODULE 1

5 MODULE OBJECTIVE

6 PMI-PBA Preparation It is based on the PMI s BA for Practitioners Practice Guide It is applicable to all programs and projects, regardless of whether these are focused on products Services process improvement.

7 INTRODUCTION TO BUSINESS ANALYSIS In the past 12 months, PMI reports (2014) evidenced the following: Only 64% of completed projects successfully met their original goals and business intent 16% of projects that started where deemed failures Inaccurate requirements gathering was reported by 37% of organisations as the primary cause of project failure Poor requirements management practices are the second leading cause of project failure, second only to changing organisation priorities

8 INTRODUCTION TO BUSINESS ANALYSIS Business Analysis focuses on solving the challenge of Requirements Management Business Analysis is the application of knowledge, skills, tools and techniques to: - Determine and Identify business needs - Recommend and Identify viable solutions - Elicit, document and manage stakeholder requirements in order to meet business need

9 INTRODUCTION TO BUSINESS ANALYSIS Business Analysis may be performed by any individual responsible for performing the work irrespective of their title.

10 Agile team members; Business architects; Roles that may perform BA Business intelligence analysts; Business process analysts; Business subject matter experts; Data, functional, operational, systems, or user experience analysts; Enterprise business analysts; Product managers or product owners; Project managers; Requirements, software requirements, systems, or value engineers; and Requirements managers.

11 INTRODUCTION TO BUSINESS ANALYSIS Requirements are conditions or capabilities required to be present in a product, service or result to satisfy a contract or other formally imposed specification -PMBOK Guide (5 th Ed.) Types include: Business, Stakeholder, Solution, Functional, Non-functional and Transition requirements

12 Requirement Types Business Requirements. Describe the higher-level needs of the organization as a whole, such as business issues or opportunities, and reasons why a project has been undertaken. Stakeholder Requirements. Describe the needs of a stakeholder or stakeholder group, where the term stakeholder is used broadly to reflect the role of anyone with a material interest in the outcome of an initiative, and could include customers, suppliers, and partners, as well as internal business roles.

13 Requirement Types Solution Requirements. Describe the features, functions and characteristics of a product, service or result that will meet the business and stakeholder requirements. Solution requirements are further grouped into: Functional Requirements. Describe the behaviors of the product. Nonfunctional Requirements. Describe the environmental conditions or qualities required for the product to be effective. Transition Requirements. Describe temporary capabilities, such as data conversion and training requirements, and operational changes needed to transition from the current state to the future state.

14 NOT Part of BA Efforts Project requirements are defined by PMI as the actions, processes, or other conditions the project needs to meet. These requirements focus on aspects of project execution. A quality requirement as defined by the PMBOK Guide Fifth Edition is a condition or capability that will be used to assess conformance by validating the acceptability of an attribute for the quality of a result.

15 It is important to note that Project and Quality requirements are not a part of business analysis efforts. These are the responsibility of the Project Manager.

16 Exercise INTRODUCTION TO BUSINESS ANALYSIS Study the image in the next slide and review the requirements from each of the stakeholders involved i.e. Management, Project Manager, Senior Analyst, Programmer, Installer and User.

17 INTRODUCTION TO BUSINESS ANALYSIS

18 COURSE STRUCTURE Introduction to Business Analysis Module 1 Needs Assessment Module 2 Business Analysis Planning Module 3 Requirements Elicitation and Analysis Module 4 Traceability and Monitoring Module 5 Solution Evaluation Module 6

19