Describe BA’s tasks to organize and coordinate the efforts of business analysts and stakeholders.
Planning the approach to carry out BA work.
Planning the BA activities.
Planning how to identify and engage with the stakeholders.
Planning how to govern the BA work — Making decisions like approving BA work, deciding on priority, etc.
Planning how to manage the information — What documents to create, how to name them, how to store them, etc.
Planning and managing the performance of BA work.
2. Elicitation and Collaboration
Describes the tasks that business analysts perform to prepare for and conduct elicitation activities and confirm the results obtained.
The most interesting BA work — (meet and talk to people)
How to prepare to elicit needs-related information from stakeholders or from other sources of information like documents, old systems etc.
How to conduct the elicitation activity and how to capture the information collected (meeting notes, voice recording, video recording, etc.)
How to play confirm the collected needs-related information by confirming from the stakeholders or other sources.
How to communicate and collaborate with stakeholders.
3. Requirement Life Cycle Management
Describes the tasks that business analysts perform in order to manage and maintain requirements and design information from inception to retirement. Tasks are describe establishing meaningful relationships between related requirements and designs, and assessing, analyzing, and gaining consensus on proposed changes to requirements and designs.
How to identify and maintain relationships between requirements and designs.
Prioritizing the requirements.
Managing the requirements by creating them, naming them, and storing them.
Making use of requirements for re-use.
4. Strategy Analysis
Describes the business analysis work that must be done to explore what is going on in the business at present, what are the problems and impact, and what must be done to make it better.
Finding details about the current situation in the business in terms of people, systems, processes, equipment, policies, etc.
What must be there in the future for the business to achieve business needs.
What should the future systems, processes, policies, people, equipment, etc. should be like.
What are the gaps between current and future state.
What are the risks and impacts of moving to the future state.
The strategy to move from the current to the better future.
5. Requirements Analysis Design Definition
Describes the business analysis work to be done to analyst, model, document, verify, and validate requirements and designs.
Creating diagrams (use case diagrams, process diagrams), specifications (use cases, user stories, etc.), and tables (state table, decision table, data dictionary)
Checking whether requirements and designs are correct.
Checking whether requirements and designs meet stakeholder needs.
Putting everything together and creating a meaningful document (like DSRS, BRD, Product Backlog)
Working with developers to communicate the requirements and designs and working with them to design and implement the solution.
6. Solution Evaluation
Describes the tasks that business analysts perform to assess the performance of, and value delivered by a solution in use by the enterprise, and to recommend removal of barriers or constraints that prevent the full realization of the value.
Checking whether the solution/design is working as expected from the prototype stage to, POC, to the actual implemented solution and beyond that.
Collecting performance details about the solution — software product, organization change, process improvement, culture change, etc.
Analyze the collected performance information • Identify limitations in the solutions.
Identify the limitations in the business that are hindering performance of the solution.
Recommend ideas to improve the solution and the business.
