Chapter 6: Strategy Analysis


posted by Liliane Castano Marino



According to chapter 6 of the BABOK, the Strategy Analysis knowledge area describes the work that must be executed to describe the tasks used to identify the business need, address that need, and align the change strategy within the enterprise.

The Strategy Analysis knowledge area is composed of the following tasks:

1)      Analyze Current State
At this point, it is important to understand the reasons why an enterprise needs to change some aspect of how it operates and what would be directly or indirectly affected by the change.  It is also important to set a baseline and context for the change.

2)     Define Future State
The purpose of defining future state is to determine the set of necessary conditions to meet the business need and define what parts of the enterprise need to change in order to meet the goals and objectives set.

3)     Assess Risks
The purpose of Assess Risks is to understand the uncertainties on the change, analyse the impact those uncertainties may have, and recommend actions to address risks where appropriate.

4)     Define Change Strategy
The purpose here is to perform and assess alternative approaches to the change and recommend the highest value approach for reaching the future state including any transition states that may be required.

Comments

  1. Paramjeet Kaur Toor24 February 2020 at 09:58

    All these strategies use many techniques to analyses these areas such as balanced scorecard, brainstorming, decision analysis, surveys , SWOT analysis are using for defining future state.
    Scotia bank also use these techniques for example by SWOT analysis they find out their strengths and opportunities which then helps Scotiabank to define future needs or requirements for achieving their goals. Moreover, change strategy is used for bringing those changes into Scotiabank that will give more efficient results.

    ReplyDelete
  2. Harvinder Singh24 February 2020 at 15:38

    Assess Risk is to identify the risk or other hazards which a bad impact on the organization. It characterizes objectives and targets that will show that the business need has been fulfilled and characterizes what parts of the endeavor need to change so as to meet those objectives and goals.To stop from these hazards, it is important to know before they become bigger for the organization. Therefore, Risk assessment is important for every business to grow in the market.

    Following are the risk on the project of the business:

    1. Cost : Risk impacts the cost of the project in organization. Generally, if there is more risk in the
    way of the project then the cost of the project will also be more to be completed the project
    on time

    2. Schedule: In the beginning of the project the employees are not be able to recognize the risk
    and when the conflict arise in the future the business analyst makes some of the changes in
    scheduling of the employees so that delays should be removed.

    Therefore, it is essential to know about the risk and take corrective actions to minimize the risk from the business.

    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