Chapter - 9


Strategies for today’s business analyst: - For today’s changing surroundings strategies are given to the business analyst to guide requirements discovery.
1.      Balancing knowledge, activities, and people: - In this, to produce optical value of business you should have full detail of your work like – when to have reviews, when to involve stakeholders, so on. This includes requirements knowledge, activities and people. Requirements knowledge includes the product which are useful for work. In activities to discover and communicate knowledge tasks and checkpoints are performed for project. People are they who are there to help you to develop this business.
2.      Knowledge is needed before each breakout: - It include the information or detail, requirements you need to have for your project so that the desire project produce best results without any restrictions. We should have enough knowledge for the project because of its breakout conditions. Various breakout conditions are external and sequential.
3.      External strategy: - In this strategy, we use solutions externally. In six activities are performed with breakout conditions for the project that are conditions for the project that are conception, scoping, work investigation, product determination, requirements definition and construction. With these activities project develops successfully.
4.      Iterative strategy: - In these products are made in a small series on a fix scale. It includes same activities as used in external strategy. The knowledge you use for this project should be visible and shareable so that people can see the result of any change and give response quickly.
5.      Sequential strategy: - In this strategy activity is completed before the beginning of next activity. Five breakdown condition are performed for the completion of this project.

Comments

  1. Kirandeep Kaur12 April 2020 at 17:16

    This chapter provides the strategies for Today's Business Analyst to guide them about the requirements discovery in today's changing environments. Strategy is a framework of Activities, Requirements Knowledge and People. The best way to discover the most suitable strategy for the project is to start with the generic profile most that looks like a current way of working and then make changes to accomplish the goals such as:
    1. Keep stakeholders involved by having frequent deliveries of artifacts, or working software.
    2. Respond to business changes more quickly.
    3. Make it easier for stakeholders to provide feedback.
    4. Avoid producing deliverables that duplicate existing knowledge, or that provide little or no new knowledge.

    ReplyDelete
  2. Kerone Barnett14 April 2020 at 21:49

    Chapter 9 describes the strategies a Business Analyst uses in Business Requirements Gathering. As mentioned in the earlier comment, at the heart of strategy, are Activities, People and Requirements Knowledge. The chapter explains three key strategies to employ - External Strategy (where the product development is outsourced to an external supplier), Iterative Strategy (where each stage of the development process is built in small increments and reviewed for compliance with expectations/ purpose ) and Sequential Strategy(completing each stage prior to moving to the next phase).

    These strategies all have some similarities and activities that commence with conception through to construction. The Business Analyst must therefore decide, based on the project at hand, which strategy best fits the product/ business and make the necessary tweaks/adjustments when applying the most appropriate strategy.

    ReplyDelete
  3. Karandeep singh23 April 2020 at 15:04

    EXTERNAL STRATEGY - Work Investigation to Building - This path is the most radical variation for this strategy: You have accumulated, and documented, sufficient knowledge of the business, and you pass that directly to the supplier with no further elaboration on your part. Your intention is either for the external supplier to design and implement a system to satisfy your business needs, or for the supplier to propose one or more of its products to satisfy as much as possible of your business needs.

    ReplyDelete

Post a Comment

Popular posts from this blog

Chapter 7 – Business Requirements Gathering

Chapter 7 –  Understanding the Real Problem This chapter focuses on the Business Analyst “thinking above the line” and focusing on the true essence of the business. This requires reviewing the Brown Cow Model – that is looking at the area above the line – the “ What Now ”. This section examines the undiluted and core reason for the business’ existence. The next step would be to look at the future of the business, called the “Future What”. Examining these two areas helps the Business Analyst get to the heart of the business problem, rather than focus on possible solutions. With the right focus the Business Analyst is not distracted by what others may think the solution could be, but the BA delves and trawls through as much information as possible to accurately understand the business and how it functions, minus technology or automation. This determination to channel all efforts towards the core purpose of the business allows the BA to be more open to all possible solutions...
Read more

Chapter 3 - Business Requirements Gathering

Chapter 3 - Scoping the Business Problem This chapter focuses on Project Blastoff Deliverables such as Project Purpose, Scope of work, Stakeholders, Constraints, Names, Estimated Cost and Risks. The chapter refers to Scope, Stakeholders and Purpose as the Trinity confirming that these are core elements of any successful project blastoff. ·          For Project Scope, we must understand the extent of the work to be done and how this task (business improvement) will impact the current operational environment and its existing products and services. We must ensure that we accurately document the depth and breadth of the project. ·          For Project Purpose, we must accurately capture the quantifiable/ measurable business benefit to be gained from the completion of the project. ·          For Stakeholders, we must document all possible persons with a vest...
Read more

Chapter 4 - BUSINESS USE CASES

Business use cases  -Business events are useful to partition the work, but it is the work’s response to the  event that now captures the interest of the requirements analyst. For every business event, there is a preplanned response to it, known as a business use case (BUC). Rabbit Projects - it is important to have a rock-solid grasp of the business problem to be solved. Rabbits make use of business use cases to explore their problem domain before starting to formulate a solution. This approach does not add to the documentation load, and it lessens the time spent delivering inappropriate solutions. Horse Projects - Horse projects are more strategic than rabbits. they need more time to complete. There is also the possibility of using Business use case scenarios as the documentation to pass along to the developers. Elephant Projects - elephant projects have a large number of stakeholders, clear communication is both important and difficult. Business ...
Read more