“BA Techniques You Can Use Everyday!” September 19, 2018 6:00PM – 8:00pm
About the Speakers – Kris Miller, CBAP Kris Miller received her CBAP certification in December 2012 and has a bachelor’s degree in International Business from San Jose State University. Kris is also currently working as a Business Analysis on-line course instructor thru the UC Davis Extension program. Kris has also previously served on the IIBA-SVC Chapter board as the 2017 VP of Membership and VP of Education & Certification in 2015. Kris is excited to share her knowledge about IIBA certifications.
About the Speakers – Tami Tactacan, CBAP Tami Tactacan has over 26 years of experience as a Business Analyst and is currently a Business Solutions Analyst at K-LOVE and Air1 Radio Networks. She was the 2016 VP of Education & Certification for the IIBA- SVC Chapter, which helped her and some of her study group participants pass the CBAP exam for the BABOK v2. She was also the 2017 IIBA-SVC Chapter President. Tami loves sharing about what she knows about obtaining her CBAP to help other analysts avoid the pitfalls she experienced.
Presentation Content Present One Technique for each BABOK Knowledge Area Overview of the Knowledge Area Overview of the Tasks Within Each Knowledge Area Review One Technique for Each Knowledge Area Perform a Technique Activity for One Task within a Knowledge Area
Business Analysis Book of Knowledge (BABOK) & Knowledge Areas The BABOK Guide is the collection of knowledge within the profession of business analysis and reflects current generally accepted practices. It describes business analysis areas of knowledge, their associated activities and tasks, and the skills necessary to be effective in their execution. 6 Knowledge Areas: Business Analysis Planning & Monitoring 1. Elicitation & Collaboration 2. Requirements Life Cycle Management 3. Strategy Analysis 4. Requirements Analysis & Design Definition 5. Solution Evaluation 6.
Business Analysis Planning & Monitoring The Business Analysis Planning & Monitoring knowledge area describes the tasks, activities and techniques that are required for successful definition and planning of business analysis project phase to achieve a controlled start. Defining and determining business analysis processes Identifying stakeholders Defining roles and responsibilities of stakeholders in the business analysis effort Developing estimates for business analysis tasks Planning how the business analyst will communicate with stakeholders Planning how requirements will be approached, traced, and prioritized Determining the deliverables that the business analyst will produce Determining the metrics that will be used for monitoring business analysis work
Business Analysis Planning & Monitoring
Business Analysis Planning & Monitoring Task: Plan Stakeholder Engagement The purpose is to plan an approach for establishing and maintaining effective working relationships with the stakeholders. Involves conducting a thorough stakeholder analysis to identify all of the involved stakeholders and analyze their characteristics. The results of the analysis are then utilized to define the best collaboration and communication approaches for the initiative and to appropriately plan for stakeholder risks. Technique : Stakeholder List, Map, Personas Used to depict the relationship of stakeholders to the solution and to one another.
Stakeholder Summary Document an inventory of Stakeholders Interests Name Project Title Project Stake Description Jane Project Primary end user Oversees development of the Doe Sponsor of project project charter, vision and solutions scope. John Executive CFO and will Approves the final requirements Smith Sponsor ultimately be and ensures they align with the accountable goals of the enterprise. Phil Quality Sample Ensures projects solutions meets Miller Assurance the quality standards of the organization.
Business Analysis Planning ACTIVITY & Monitoring Pair up Think of a recent project How many stakeholder personas were there? What would you put on the listing?
Elicitation & Collaboration The knowledge area is considered the main path for discovering requirements and design information. It describes the tasks a business analyst performs to obtain and confirm information from stakeholders. It is collaborative It is not a “phase” It is ongoing as long as analysis work is occurring Should not be considered an “isolated” activity May trigger additional elicitation activities to obtain details to fill in gaps and increase understanding
Elicitation & Collaboration
Elicitation & Collaboration Task: Conduct Elicitation The purpose of Conduct Elicitation is to draw out, explore, and identify information relevant to the change. Stakeholders may collaborate in elicitation by: Participating and interacting during the elicitation activity, and Researching, studying, and providing feedback on documents, systems, models, and interfaces. Technique : Observation Used to gain insight about how work is currently done, possibly in different locations and in different circumstances.
ACTIVITY Elicitation & Collaboration Following Directions
Requirements Life Cycle Management Describes the tasks that business analysts perform in order to manage and maintain requirements and design information from inception to retirement. Maintain relationships between requirements, designs, solution components and other work products Ensure accuracy and relevance of requirements and designs Facilitate reuse of requirements and designs where appropriate Understand the value, urgency and risks associated with requirements and designs Evaluate new and changing stakeholder needs Help stakeholders reach agreement on requirements and designs
Requirements Life Cycle Management
Requirements Life Cycle Management Task: Prioritize Requirements The purpose of Prioritize Requirements is to rank requirements in the order of relative importance. Prioritization is the act of ranking requirements to determine their relative importance to stakeholders. When a requirement is prioritized, it is given greater or lesser priority. Technique : Prioritization Used to gain an understanding of a single or small group of stakeholders' basis of prioritization or priorities.
Requirements Life Cycle ACTIVITY Management Write your 5 top priorities in buying a car – one per index card We will put you in groups
Strategy Analysis Describes the business analysis work that must be performed to collaborate with stakeholders in order to identify a need of strategic or tactical importance (the business need), enable the enterprise to address that need, and align the resulting strategy for the change with higher and lower-level strategies. Define the future and any transition states needed to address the business need. Discover possible solutions to apply the capabilities of the organization in order to reach the desired set of goals and objectives. Ongoing activity as changes in the business need occurs or new information results in an adjustment to the change strategy. Strategy may be captured in a strategic plan, product vision, business case, product roadmap or other artifacts.
Strategy Analysis
Strategy Analysis Task: Define Current State The purpose of Analyze Current State is to understand the reasons why an enterprise needs to change some aspect of how it operates and what would be directly or indirectly affected by the change. Technique : Process Modelling Describes how work occurs within the current solution.
ACTIVITY Strategy Analysis Making a Pizza What are the steps? How do we know we are done?
Requirements Analysis & Design Definition The Requirements Analysis and Design Definition knowledge area describes the tasks that business analysts perform to structure and organize requirements discovered during elicitation activities, specify and model requirements and designs, validate and verify information, identify solution options that meet business needs, and estimate the potential value that could be realized for each solution option. Describe requirements using analytical techniques Ensure requirements and designs are internally consistent and high quality Ensure requirements and designs deliver business value Structure requirements and designs so they cohesively support the business purpose Identify potential solutions Recommend the solution that provides the greatest overall value
Requirements Analysis & Design Definition
Requirements Analysis & Design Definition Task: Specify & Model The purpose of Specify and Model Requirements is to analyze, synthesize, and refine elicitation results into requirements and designs. Technique : Scope Modeling Used to visually show a scope boundary.
Requirements Analysis & PRESENTATION Design Definition Scope Diagram
Sample Scope Diagram – Cafeteria Ordering System
Recommend
More recommend
