“BA Techniques You Can Use Everyday!”
September 19, 2018 6:00PM – 8:00pm
Use Everyday! September 19, 2018 6:00PM 8:00pm About the Speakers - - PowerPoint PPT Presentation
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 bachelors degree in International Business from San
September 19, 2018 6:00PM – 8:00pm
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.
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
Tami loves sharing about what she knows about
pitfalls she experienced.
Present One Technique for each BABOK
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
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:
1.
Business Analysis Planning & Monitoring
2.
Elicitation & Collaboration
3.
Requirements Life Cycle Management
4.
Strategy Analysis
5.
Requirements Analysis & Design Definition
6.
Solution Evaluation
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
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
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.
Name Project Title Project Stake Description
Jane Doe Project Sponsor Primary end user
solutions Oversees development of the project charter, vision and scope. John Smith Executive Sponsor CFO and will ultimately be accountable Approves the final requirements and ensures they align with the goals of the enterprise. Phil Miller Quality Assurance Sample Ensures projects solutions meets the quality standards of the
Pair up Think of a recent
How many
What would you
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
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.
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
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.
Write your 5 top
We will put you in
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.
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.
The Requirements Analysis and Design Definition knowledge area describes the tasks that business analysts perform to structure and
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
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.
The Solution Evaluation knowledge area describes the tasks that business analysts perform to assess the performance of and value delivered by a solution in use by the enterprise, and to recommend removal of barriers or constraints that prevent the full realization of the value.
Determine how the performance of a solution will be assessed Assess solution performance to understand value delivered Investigate solution issues that may be leading to poor performance Investigate issues external to the solution that may be leading to
poor performance
Identify actions that can be taken to increase the value delivered by
a solution
Task: Recommendations on Solutions
The purpose of Specify and Model Requirements is to
analyze, synthesize, and refine elicitation results into requirements and designs.
Technique: Decision Matrices
Used to visually show a scope boundary.
Criteria ABC Solution Sam’s Software Joe’s JAVA Carrie’s Comp One Time Set up Fees $0 – part of our current solution $1,000 $0 $1,500 Annual Cost $8,000 $14,500 $8,950.00 $5,000 Discounts? 3yr Contract; NP discount NP discount No NP Discount No NP Discount Customers Us, NCR, Hertz NY Times, Red Cross n/a CCP and other small companies Reporting Expanded dashboards limited n/a n/a Data Import capability/Int. Unlimited import Unlimited import 2 imports a year n/a Summary Known vendor, integrates well with us Could be a good solution but pricey Could be a good solution but reporting is needed Not compatible with our needs Grade A B B C
Criteria (Weight)
Items to be ranked Increase Revenues (Weight .3) Decrease Claims (Weight .4) Ease of Implementatio n (Weight .2) Cost (Weight .1) Total Votes Final Rank XYZ Software Package 1 X .3 = .3 1 X .4 = .4 1 X .2 = .2 2 X .1 = .2 1.1 2 Develop smartphone interfaces in- house 2 X .3 = .6 2 X .4 = .8 1.4 1 Outsource interface development 2 X .2 = .4 1 X .1 = .1 .5 3
1.
Business Analysis Planning & Monitoring
Tasks: Plan Stakeholder Engagement
Technique: Stakeholder List, Map, Personas
2.
Elicitation & Collaboration
Task: Conduct Elicitation
Technique: Observation
3.
Requirements Life Cycle Management
Task: Prioritize Requirements
Technique: Prioritization
4.
Strategy Analysis
Tasks: Define Current State
Technique: Process Modeling
5.
Requirements Analysis & Design Definition
Task: Specify & Model
Technique: Scope Modeling
6.
Solution Evaluation
Task: Recommendations on Solutions
Technique: Decision Matrices
4.
Tasks: Define Current State
Technique: Process Modeling
5.
Task: Specify & Model
Technique: Scope Modeling
6.
Task: Recommendations on Solutions
Technique: Decision Matrices