Documente Academic
Documente Profesional
Documente Cultură
Purpose:
- Specify how the business analysis tasks will be performed - Identify the deliverables to be produced
Value:
- Specifies tools, resources and contributors & ensures availability - Allows for monitoring & addressing of requirements challenges - Coordinates with other project work
Business Analysis Planning and Monitoring IIBA Operational Vision Inputs and Outputs
2.1.7 - Output
Business Analysis Approach
10
11
12
13
14
15
16
17
18
19
20
2.3.7 Output
Business Analysis Plans
21
22
23
24
Project Type
A new, customized in-house software development project. (all requirements) Upgrading the technology or infrastructure of a current system. (technical requirements) Change in a business process or new data for an existing application. (process and data requirements, business rules, functional and technical requirements ) Purchase of a software package. (Request For Proposal, and the package will need to include the business requirements, technical requirements, limited functional requirements and other vendor specifications) Short, focused, agile style iterations of software development (very little formal requirements documentation)
25
26
2.4.7 Output:
The stakeholder communications requirements for business analysis activities Format, content, medium, level of detail. Responsibility for collecting, distributing, accessing, and updating information.
27
28
29
30
31
2.5.6 Stakeholders:
Domain SME End User Implementation SME Operational Support Project Manager Tester Sponsor
32
33
34
35
36
37
2.6.7 Output:
Business Analysis Performance Assessment Business Analysis Process Assets
38
Questions?
39