Chapter 3: Business Analyst Planning and Monitoring By, Hassan Kamara






Business Analysis Planning and Monitoring

According to chapter 3 of the BABOK, the tasks of business analysis planning and monitoring are presented to coordinate the efforts of stakeholders and BA’s.

The 5 main knowledge areas that will be covered are:

Ø  Plan business analysis approach

Ø  Plan stakeholder engagement

Ø  Plan business governance

Ø  Plan business analysis information management

Ø  And identify business analysis performance improvements



1.      Plan business analysis approach.

Plan business analysis approach can be defined to be the planning of business analysis work from selection or creation of a methodology to planning the individual tasks, activities and deliverables. BA’s also identify initial techniques that could be applied. The approach is used to define a method to conduct the business analysis activities. The approach should; align to the goals of he change, coordinate the business analysis deliverables and activities with the tasks of the overall change, include risk management tasks that help to reduce the quality of business analysis deliverables or impede task efficiency and leverage approaches, tools and select techniques that have worked well in the past.


2.      Plan Stakeholder Engagement

Stakeholder engagement is completing a stakeholder analysis to find all of the stakeholders that are involved and to analyze their characteristics. After the analysis is complete the results will then be used to define the best communication and collaboration approaches to appropriately plan for stakeholder risks. Stakeholder engagement planning is used to establish and maintain effective working relationships with stakeholders.


3.      Plan Business Analysis Governance

It is a BA’s job to ensure that a governance process is in place and to also clarify and doubts with it. An operational governance process can process information required for decisions and can identifies decision makers. An operational governance process can describe how prioritization and approval decisions are made for designs and requirements. Key identifiers for planning the governance approach are; How BA work will be prioritized and approached, who has the authority to approve changes, how changes will be communicated and documented, who has responsibility for analyzing change requests and more. The overall purpose is to define how decisions are made about designs and requirements including, reviews, change control, prioritization and approvals.


4.     Plan Business Analysis Information Management

BA information is compiled of any and all info that BA’s create, compile and elicit while performing business analysis. Stakeholder concerns, elicitation results, scope statements, models, designs, requirements and solution options are examples of this. Information management can help to make sure that BA information gets organized in a useful and functional manner, is accessed easily to the appropriate people and gets stored for the necessary amount of time. Information management involves identifying:

·        how info should be organized,

·        how info should be stored and accessed,

·        characteristics about the info that must be maintained.

·        And more.

The overall purpose is to develop an approach for how BA information gets accessed and store. 


5.      Identify Business Analysis Performance Improvements

To improve and monitor performance, its necessary to establish performance measures, report on analysis results, conduct the performance analysis as well as identify the preventative, corrective or development actions. PA (performance analysis) should happen throughout an initiative. Once the initial potential performance improvements are found they can then become a guideline for the next time a task is executed. The overall purpose of identifying business analysis performance is to assess BA work and to plan process improvements where required.

Comments

  1. Liliane Marino3 February 2020 at 13:03

    It is also important to mention the related outputs of each of these tasks, as follows:
    1) Business Analysis Approach – set the business analysis approach and activities that will be executed through an initiative.
    2) Stakeholder Engagement Approach – contains information regarding the identified stakeholders as: characteristics and roles and responsibilities for the change.
    3) Governance Approach – recognizes the stakeholders who will have the responsibility and authority to make decisions about business analysis work. It also determines the process to be used to manage requirement and design changes throughout the initiative.
    4) Information Management Approach – includes the definition about how business analysis information will be stored, accessed and utilized during and after the change.
    5) Business Analysis Performance Assessment – shows the difference between the planned versus actual performance, including findings to help understand the performance of processes.

    ReplyDelete
  2. Paramjeet Kaur Toor3 February 2020 at 16:18

    As business analysis approach used to plan business analysis work and individual's activities. Similar, Scotia bank also use this approach for planning business and cover many elements such as roles of key player, financing, Taxation and legal considerations, Retirement and estate considerations, business strategies, timetable etc. Tools that Scotia bank is using are solutions builder, marketing tools, Scotiabank Ownership Transition Tool and many other.

    ReplyDelete
  3. Harvinder Singh4 February 2020 at 19:54

    The process of how a business analyst determines which activities will be needed to complete the business analysis effort. The tasks within this knowledge area show the business analysis tasks in all of the other knowledge areas. The Business analysis approach is used to define a method to conduct the business analysis activities. Scotia bank is also use this approach to plan future business outcomes. The information management approach tells the business analytical information will be stored, accessed and utilized before and after the change.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 8 - Starting the Solution by Harvinder Singh

  Chapter 8 Starting the Solution We are transferring from an abstract global to the physical international, from policy to technology, from problem to solution; from purpose to design: we have reached the closing quadrant of the Brown Cow Model, in which will be determined how we are going to enforce the essential business. With a solid know-how of the essence of the business, which means that the real trouble to be solved, it’s time to determine which components of that problem would advantage from being automated. The commercial enterprise analyst juggles many factors to determine the most appropriate product to build. Iterative Development Iterative development is a way of breaking down the software improvement of a large application into smaller chunks. In iterative development, feature code is designed, developed and examined in repeated cycles. With each iteration, additional functions may be designed, advanced and examined till there is a com...
Read more

Chapter 4- Business Use Cases - posted by Chelsia Palta

Understanding the Work  The product you intend to build must improve its owner’s work; it will be installed in the owner’s area of business and will do part of the work. It does not matter which kind of work it is commercial, scientific, embedded real-time, manual, or automated you always have to understand it before you can decide which kind of product will best help with it. Use Cases and Their Scope The term "use case" was coined by Ivar Jacobson back in 1987 as a way to describe an interaction between a system and a user of that system. Jacobson needed to break the system into smaller units, as he felt that object models were not scalable. Thus, to conquer the complexity and largeness of modern systems, he said it was first necessary to partition them into convenient chunks, and that these chunks should be based on the user’s view of the system. The Outside World Adjacent systems behave like any other systems: They contain processes and consume and/or...
Read more

Chapter 11 Non-Functional Requirements by Hassan

Non-Functional Requirements Non-Functional Requirements can be generalized as "what a product/system is supposed to be. these requirements tend to be qualities that the product should have and they should specify how well the product does what it does. the requirements should either make the product usable, fast, reliable, attractive or safe and they should describe the character/ the way the functions should behave. Look and Feel Requirements the look and feel requirements are key to the non-functional requirements and as a BA one must consider them for every project. These requirements can describe how a product/system's desired appearance, mood, spirit or overall style/ appearance. The look and feel requirements can further specify what the product/system intends to appear as and is not a detailed design of the product/system itself. The typical look and feel requirement should be simple to use, professional looking, attractive to its market, consistent with previ...
Read more