CAPM MOD 4 Flashcards
- Strategic business analysis
- Eliciting and analyzing requirements
- Feasibility studies and definition of new business opportunities
- Scoping and opportunity and identifying a preliminary solution
- Preparation of a business case for a solution
- Monitors changes in requirements and updates the appropriate documents
- Suggest methodologies for planning
- Work with diverse stakeholders to determine who can best help with business needs
Functions of a business analyst
condition or capability that is necessary in a product, service, or result to satisfy a business need from stakeholders like legal, customers, etc.
Requirement
where requirements are tracked
Requirement traceability matrix
another place requirements can be tracked as “user stories”
Product backlog
can capture stakeholder needs; must focus on what the need is and not how to deliver on it
Ex: customers want to view available seats before ticket is purchased
User stories
high level statement of a business objective or goal; why a project should be undertaken (any requirements that’s not technical).
o Formula: To _ the company must _
Business requirement
specific characteristics of a solution
- Solution requirements
describe solution’s specific behaviors ex: calculate total ticket cost including local sales tax
functional requirement
describe environmental conditions or qualities for the product to be effective ex: system must support 10,000 concurrent connections to be able to show available seats
non functional requirement
how solution will be deployed and released into production.
o Temporary and not done again after project is done
Ex: trained support staff available during first month
transition requirements
how the requirements will be analyzed, documents, and managed
Requirements management plan
table of business rules and related attributes
business rules catalog
user stories are further detailed with additional information until ready for development
story elaboration
conditions that team agrees to complete before user story is considered understood so that work can begin to construct it
definition of ready
split epics or user stories from higher to lower level
story slicing
all definitions for terms and acronyms about a product
glossary
describes system user interactions to achieve successful completion of goal. Frequently used to identify and elaborate requirements
use case
, business analyst creates requirements, puts them in a requirements traceability matrix, as they work with the project team, their role will be to ensure work delivers business value
predictive approach
business analyst creates user stories, puts them in a product backlog, and their role will be to maintain alignment between business need and project deliverables and minimize changes
adaptive approach
process of gathering and analyzing information to determine whose interest should be taken into account throughout the project. Must keep confidential
stakeholder analysis
o continuous cycle that ends until the project ends
Identify
Understand
Analyze
Prioritize
Engage
Monitor
o Want to understand their power (authorize or decision making), impact (scope, costs, timelines), attitude (pos or neg), beliefs (approaches, convictions), expectations, influence (extent of using their power), proximity (how close their role is associated with project), interest (micromanage because they are so interested/vested in it)
Six stages of stakeholder analysis
external, project and product team, business, management
4 types of stakeholders
Defines roles of stakeholders
R – person who owns project task/work
A – Person who signs off on work, judging competition and how it meets standards
C – people who have ability or knowledge to complete work so they provide feedback
I – people who must be kept informed but not necessarily consulted
Responsibility assignment matrix
structured sequential progression among well-defined phases
Usually do the planning and predicting requirements before project starts. Changes can create risks.
predictive approach
Performs the same business analysis tasks as they do in predictive but repeatedly since information comes as the project progresses. Don’t know all requirements or the depth of them upfront, they keep evolving as project goes on.
Agile/Adaptive approach
