BAPM - Details Flashcards
1
Q
Considerations that may affect the appropriate level of formality for the intiative
A
- change is complex and high risk
- organization is in , or interacts with, heavily regulated industries
- contracts or agreement necessitate formality
- stakeholders are geographically distributed
- resources are outsourced
- staff turnover is high and / or team members may be inexperienced
- requirements must be formally signed off
- business analysis information must be maintained long-term or handed over for use on future intiatives
2
Q
Items included when integrating BA activities in the BA approach
A
- identifying the activities required to completed deliverables
- dividing the work into iterations
- using a previous similar initiative as an outline
3
Q
Things that can affect timing of BA activities for a change initiative
A
- approach (predictive - phases; adaptive - iterative)
- the availability of resources
- priority and / or urgency of the intiative
- other concurrent intiatives
- constraints such as contract terms or regulatory deadlines
4
Q
Factors that can affect BA approach complexity
A
- number of stakeholders or BA resources
- size of change
- number of business areas or system affected
- geographic and cultural considerations
- technological complexities
- risks that could impede the BA effort
5
Q
Factors that can affect BA approach risk
A
- experience level of the BA
- extent of domain knowledge held by the BA
- level of experience stakeholders have in communicating their needs
- stakeholder attitudes about the change and business analysis in general
- amount of time allocated by stakeholders to the BA activities
- any pre-selected framework, methodology, tools, and / or techniques imposed by organizational policies and practices
- cultural norms of the organization
6
Q
Things about which BA’s analyze stakeholder attitudes
A
- business goals, objectives of the initiative, and any proposed solutions
- business analysis in general
- the level of interest in the change
- the sponsor
- team members and other stakeholders
- collaboration and a team-based approach
7
Q
Ways to uncover / identify stakeholders
A
- internal
- orginizational chart
- business processes
- sponsor
- external
- understanding any existing contracts in place
- anticipated vendors that may have a role based on existing relationships with the organization
- regulatory and governing bodies that may influence the work
- shareholders
- customers
- suppliers
8
Q
Considerations when planning stakeholder collaboration
A
- timing and frequency of collaboration
- location
- available tools such as wikis and online communities
- delivery method such as in-person or virtual
- preferences of the stakeholders
9
Q
Stakeholder communication needs evaluated by the BA
A
- what needs to be communicated
- what is the appropriate delivery method (written or verbal)
- who the appropriate audience is
- when communication should occur
- frequency of communication
- geographic location of stakeholders who will receive communications
- level of detail appropriate for the communication and stakeholder
- level of formality of communications
10
Q
Items identified by BA’s when planning the governance approach
A
- how BA work will be approached and prioritized
- what the process for proposing a change to BA information is
- who has the authority and responsibility to propose changes and who should be involved in the change discussions
- who has the responsibility for analyzing change requests
- who has the authority to approve changes
- how changes will be documented and communicated
11
Q
Things BA’s do when developing a change control process
A
- determine the process for requesting changes
- determine the elements of the change request
- cost and time estimates
- benefits
- risks
- priority
- course(s) of action
- determine how changes will be prioritized
- determine how changes will be documented
- determine how changes will be communicated
- determine who will perform the impact analysis
- determine who will authorize changes
12
Q
Things determined by the BA when planning the prioritization process (governance)
A
- formality and rigour of the prioritization process
- participants who will be involved in prioritization
- process for deciding how prioritization will occur, including which prioritization techniques will be utilized
- criteria to be used for prioritization; for example, requirements may be prioritized based on cost, risk, and value
13
Q
Items identified as part of information management
A
- how information should be organized
- the level of detail at which information should be captured
- any relationships between the information
- how information may be used across multiple initiatives and throughout the enterprise
- how information should be accessed and stored
- characteristics about the information that must be maintained
14
Q
Things that must be taken into account when determining how to best structure and organize BA information
A
- type and amount of information to be collected
- stakeholder’s access and usage needs
- size and complexity of the change
15
Q
Basis for determining the traceability approach
A
- complexity of the domain
- number of views of requirements that will be produced
- any requirement-related risks, organizational standards, applicable regulatory requirements
- understanding of the costs and benefits involved with tracing
- goal is to use an approach at a level of detail to add value without excessive overhead
