Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
15 Cards in this Set
- Front
- Back
- 3rd side (hint)
What are the tasks in Business Analysis Planning and Monitoring? |
– plan business analysis Approach |
ASACMP („ace camp“: a camp for BAs to do planning) |
|
Plan Business Analysis Approach |
specify: - overall process (plan-/change-driven) - team roles - deliverables - analysis techniques - timing and frequency of stakeholder interactions |
|
|
Conduct Stakeholder Analysis |
identify or determine: – appropriate stakeholders – authority levels (for BA work) |
|
|
Responsibility Assignment Matrix (RACI)
|
Describes the participation by various roles in completing tasks or deliverables for a project or business process: |
|
|
Stakeholder Matrix
|
A stakeholder map that often include lines of communication between stakeholders. It shows the influence of and impact to stakeholders. |
|
|
Plan BA Activities
|
specify: - scope of work for BA activities - BA deliverables - BA activities (WBS) incl. - estimates for activities - time plan with milestones - how to tailor the plan
|
|
|
Plan BA Communication |
Determine how to receive, distribute, access, update, and escalate information (what, to whom, when, how). It includes: - stakeholder communications requirements - format, content, medium, - level of detail, - level of formality - frequency - responsibility for collecting, distributing, accessing, and updating information |
|
|
Plan Requirements Management Process |
Determine: - how to structure traceability - requirements attributes - requirements change process - which stakeholders approve change - prioritization process - how to tailor the plan |
|
|
Manage BA Performance
|
Determine/identify: - metrics to measure the performed work - process to track, assess and report on BA performance - preventive and corrective actions |
|
|
Techniques used in Plan BA Approach
|
- Decision Analysis |
|
|
Organizational Process Assets
|
Policies and procedures, suggested methodologies, templates and guidelines. E.G. previous BA approaches |
|
|
WBS
|
Decomposes the project scope into smaller and smaller pieces, creating a hierarchy of work. |
|
|
Repository
|
A place or method for storing and retrieving things.
|
|
|
Traceability |
The ability to track a requirement through the development life cycle. It should be bi-directional to trace requirements back to the business need and forward through implementation. |
|
|
Name typical Requirements Attributes |
- Complexity |
CARAS SOUPS |