CAPM MOD 4 Flashcards

1
Q
  1. Strategic business analysis
  2. Eliciting and analyzing requirements
  3. Feasibility studies and definition of new business opportunities
  4. Scoping and opportunity and identifying a preliminary solution
  5. Preparation of a business case for a solution
  6. Monitors changes in requirements and updates the appropriate documents
  7. Suggest methodologies for planning
  8. Work with diverse stakeholders to determine who can best help with business needs
A

Functions of a business analyst

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

condition or capability that is necessary in a product, service, or result to satisfy a business need from stakeholders like legal, customers, etc.

A

Requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

where requirements are tracked

A

Requirement traceability matrix

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

another place requirements can be tracked as “user stories”

A

Product backlog

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

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

A

User stories

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

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 _

A

Business requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

specific characteristics of a solution

A
  • Solution requirements
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

describe solution’s specific behaviors ex: calculate total ticket cost including local sales tax

A

functional requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

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

A

non functional requirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

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

A

transition requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q
A
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

how the requirements will be analyzed, documents, and managed

A

Requirements management plan

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

table of business rules and related attributes

A

business rules catalog

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

user stories are further detailed with additional information until ready for development

A

story elaboration

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

conditions that team agrees to complete before user story is considered understood so that work can begin to construct it

A

definition of ready

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

split epics or user stories from higher to lower level

A

story slicing

17
Q

all definitions for terms and acronyms about a product

A

glossary

18
Q

describes system user interactions to achieve successful completion of goal. Frequently used to identify and elaborate requirements

A

use case

19
Q

, 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

A

predictive approach

20
Q

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

A

adaptive approach

21
Q

process of gathering and analyzing information to determine whose interest should be taken into account throughout the project. Must keep confidential

A

stakeholder analysis

22
Q

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)

A

Six stages of stakeholder analysis

23
Q

external, project and product team, business, management

A

4 types of stakeholders

24
Q

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

A

Responsibility assignment matrix

25
Q

structured sequential progression among well-defined phases
Usually do the planning and predicting requirements before project starts. Changes can create risks.

A

predictive approach

26
Q

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.

A

Agile/Adaptive approach