1
Q
How are requirements validated with waterfall delivery?
A
- Done before solution design
- Agreed by: sponsor, business owner, SMEs, solution architects, devs, testers, PMO + BAs
- Formal requirement validation document produced containing all requirements for the project
2
Q
How are requirements validated with Agile delivery?
A
- Story level validation by SMEs (story dev) and PO, devs + testers (3As
- Occurs continuously through the project
3
Q
What are the 2 types of traceability?
A
- Vertical: back up to objectives + business case
- Horizontal: relationship with other requirements
4
Q
Briefly explain change management
A
- Changes to requirements
- Particularly difficult in waterfall as need to submit change request
5
Q
What needs to be considered in a change request?
A
- Identify the change
- Assess the impact
- Understand the choices
- Choose how to resolve
Foundation Business Analysis
flashcards
Decks in class (14)
# Cards
-
Section 1 - What is Business Analysis (5%)9
-
Section 2 - Competencies of a BA (2.5%)5
-
Section 3 - Strategic context for Business Analysis (7.5%)17
-
Section 4 - Business Analysis Service Framework (2.5%)7
-
Section 5 - Investigating the business situation (12.5%)27
-
Section 6 - Analysing + Managing Stakeholders (10%)6
-
Section 7 - Improving Business Services and Processes (12.5%)18
-
Section 8 - Defining solutions (7.5%)4
-
Section 9 - Making the Business Case (5%)12
-
Section 10 - Establishing requirements (10%)7
-
Section 11 - Documenting + Modelling requirements (10%)8
-
Section 12 - Validating + Managing requirements (5%)5
-
Section 13 - Delivering requirements (5%)16
-
Section 14 - Delivering the business solution (5%)10
