Home / Summaries / Class notes - Business Analysis / solution-analysis-business

Business Analysis

6 important questions on Business Analysis

Mention at least five elicitation techniques.

Brainstorming, Focus Groups, Interviewing, Observation, Prototyping, Requirements Workshop, Survey/Questionnaire, Document Analysis, Interface Analysis

Tell something about the Requirements Analysis area of the BABOK.

- It focuses on analyzing the data
- The methods, tools, techniques to structure raw data collected during elicitation are defined
- It identifies the gaps in requirements
- The "solution" capabilities are defined and these serve as the foundation for selecting among solution alternatives (the solution can be made when you know the implementations)
- It answered the question "What must the solution do?"

Tell something about the Requirements Management and Communications of the BABOK.

- Here is a focus on presenting and communicating documented requirements to all stakeholders, including project team members, to bring the group to consensus on project scope
- The change will be indentified and managed
- The question "Does everyone understand and agree?" will be answered

Tell something about the Solutions Assessment & Validation area of the BABOK.

- Here is a focus on ensuring that the best approach is chosen, that the solution will meet stakeholder objectives, that the solution is feasible, and that the solution guides "verification"
- The question "Does the solution do what it is supposed to do?" will be answered

Mention at least three of the underlying competencies of a business analyst?

- Analytical thinking and problem solving
- Behavioural characteristics: ethics, personal organization, trustworthiness
- Business knowledge
- Communication skills
- Interaction skills: facilitation and negotiation, leadership and influencing, teamwork
- Software applications

What are goals for doing business analysis?

- To deliver feasible quality solution that meets the business needs: the optimal solution
- Help prevent scope creep (start small, but when busy you see that the problem is actually bigger), and reduce project risks, including rework
- Provide traceability to business goals