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 vested interest in the product/ service. Users are considered to be anyone who directly/ indirectly uses the product/ service, maintains the product/ service and anyone who provides support for the product/ service. Key project stakeholders also include the Project Sponsor and Customer. Other stakeholders may include Consultants, Regulators/ Government Authorities, John Public and Special Interest Groups.
  • ·         For Project Constraints, we must carefully consider any design/ technical specifications, time or financial restrictions that may impact the project delivery.
  • ·         For Project Names, it is important to use names that all stakeholders appreciate, can relate to and understand relative to the project at hand.
  • ·         For Estimating Project Cost, we must use a practical approach – measuring product/ service functionality and using an appropriate method for costing
  • ·         For Risk Assessment, use the project deliverables from the blastoff exercise to determine what risks are possible and what risks need to be mitigated/ eliminated altogether to prevent project delays/ budget depletion.


Hosting Project Blastoff meetings to review the project deliverables and using other business management techniques clearly describe the recommended approach to scoping the business problem. This process will help a company to determine if a project will be successful or not.

Comments

  1. Kirandeep Kaur26 March 2020 at 19:46

    Every project must have a clear understanding of its goals and for any project there is always need a scope, stakeholders and goals. Scope, stakeholders and goals are known as trinity. If you understand your project properly, then you can make the right product. Scope of the work defines a part of the real-life organization and indicates the stakeholders who are interested in the work and they decide the goals for the project. If you are making a product, you cannot proceed without a sponsor because sponsor pays for the development of the product. Once the product is developed, customers buy it if this products is valuable, useful and pleasurable for them.

    ReplyDelete
  2. Karandeep singh2 April 2020 at 12:26

    Purpose of the project: a quantified statement of what the product
    is intended to do, and what benefit it brings to the business. This
    statement of purpose is an explanation of why the business is investing
    in the project, along with the business benefit it wants to achieve.
    This justifies the project and serves as a focus for the requirements
    discovery process.

    ReplyDelete
  3. Sukhpreet Singh2 April 2020 at 19:52

    Project scope is the essential part of the project. The project manager owns the project and business analyst owns the product. In project scope features and functions of the project, service and result is defined. Project scope is the result of the project or the solution to the problem. Costs and time is determined by the project manager with the help of product scope, business analyst’s report and solution to the problem. It also defines that who has the problem, why is needs to be solved and what are the situations which may arise due to the problem.

    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 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