Skip to main content

Posts

Showing posts from February, 2020

Chapter 6 - Strategy Analysis

Strategy Analysis Strategy is a  plan of action or policy that deigned to work in the most effective way to apply the capabilities of an enterprise in order to reach a desire set of goals and objectives. On the other hand, strategy analysis refers to the process of conducting research on a company and its environment to formulate a strategy  that  must be performed to collaborate with stakeholders in order to identify a need of  strategic or tactical importance (the business need), enable the enterprise to  address that need, and align the resulting strategy for the change with higher and  lower-level strategies. The Strategy Analysis knowledge area includes the following tasks: • Analyze Current State :   C urrent state analysis  is a process management strategy that identifies and evaluates a business's current  processes and  understands the business need and how it relates  to the way the enterprise functions today.  • Define Future State:   Defines goals and o

Chapter 4 - Elicitation and Collaboration

 Elicitation and Collaboration Elicitation with the engagement of stakeholders are the tasks that Business Analysts perform to get information from stakeholders or other sources and confirm the results obtained. Elicitation and collaboration is never a 'phase' in Business analysis, rather it goes on until the Business Analyst finishes his/her work. Elicitation and collaboration can be planned, unplanned, or both. The Elicitation and Collaboration knowledge area is composed of the following tasks: • Prepare for Elicitation • Conduct Elicitation • Confirm Elicitation Results • Communicate Business Analysis Information  • Manage Stakeholder Collaboration The Core Concept Model in Elicitation and Collaboration: Prepare for Elicitation: This task involves clarifying the scope of the selected elicitation techniques, collecting the required information and making schedules.  Business analysts prepare for elicitation by defining the desired outcomes of

Chapter-5 Requirements Life Cycle Management.

Requirement Life Cycle Management. The knowledge area which depicts the jobs that B.A's undertook in order to manage, organize and maintain requirements and designs information from inception to retirement. These jobs maintains meaningful relationships between connected requirements and designs. The purpose of Requirement Life Cycle Management is to make sure that the business, stakeholder, and solution requirements and designs aligned to each other and that the solution implements them. It also helps to ensure that business analysis is available for future use.  The Requirements Life Cycle: Starts with representation of a business need as a requirement. Continue through the development of a solution. Ends when a solution and the requirements that represent it are retired. The management of requirements  does not end once a solution is implemented. Throughout the life of a solution, requirements continue to provide importance when they are managed appropriat

Chapter 3- Business Analysis Planning and Monitoring

Business Analysis Planning and Monitoring The Business Analysis Planning and Monitoring knowledge area is the process of determining which activities will be required to organize and coordinate the tasks of Business analysts and stakeholders and are used to produce the required output that act as the key guidelines for other tasks. The core concepts of a Business Analysis Planning and Monitoring include: Change, Need, Solution, Stakeholders, Value and Context The Business Analysis Planning and Monitoring includes tasks explained here: 1.   Plan Business Analysis Approach : This purpose of this approach is used to describe the overall method and techniques followed to determine how and when the tasks will be performed and what deliverables are to be produced. ·       Inputs: Needs: The approach of Business Analysis is shaped according to the need of the company. It is necessary to consider what is the ne