Chapter 8 - Starting the solution

ITERATIVE DEVELOPMENT
Iterative development techniques don't always appear to do much in the way of upfront design, relying instead on frequent releases of software to gauge the design’s suitability.

ESSENTIAL BUSINESS
The functional needs can be presented to you in the form of a business use case scenario, a collection of atomic functional requirements, or properly crafted user stories. The non-functional needs are largely responsible for specifying the kind of user experience appropriate for the intended audience.

DESIGNING THE USER EXPERIENCE
Designing the whole of the user experience is the best way to come up with a product that makes people want to buy it and/or use it. Experience design aims to produce a usage experience that is pleasing and exciting, as well as relevant to the culture and aspirations of the user. Such design focuses much more on how the product makes the user feel than on adding functionality to the product.

INNOVATION
Innovation means thinking differently about the problem to find a new and better way to do the work, or in some cases to find better work to do. Instead of rushing ahead with the first-to-mind solution or the obvious solution, we urge you to spend just a little time with fellow business analysts and other stakeholders to come up with something better, something that will be longer lasting and more appealing, something innovative.

PRODUCT USE CASE SCENARIOS
The business analyst uses product use case (PUC) scenarios to communicate the intention of the automated product to the stakeholders. Naturally, the PUC scenario is not the only document available to you at this time. Even so, because it shows the functionality of the product, it is an easy document with which to convey your intentions to the stakeholders.

Comments

  1. Kirandeep Kaur12 April 2020 at 16:59

    In this chapter 'Starting the Solution', the essence of the business comes into the technological world of the implementation. The atomic functional needs are presented in the form of a Business Use Case (BUC) scenario. A persona is a virtual character that represents a large number of users with similar characteristic and persona is used by the business analyst and designer. The goal of the experience design means to produce a usage, pleasing and exciting experience. Innovation means think differently to find a new and better way to do the work by understanding the problem.

    ReplyDelete
  2. Kerone Barnett14 April 2020 at 20:54

    Chapter 8 focuses on the last quadrant of the Brown Cow Model - The Future How? This brings the model full circle from prior chapters - moving from the essence/ undiluted purpose of the business to the implementation of technological influences to improve the business. To start the solution, we must involve the relevant stakeholder input, include all agreed upon innovations and develop a prototype or an interface to monitor the development process. The product design must take into account the intended experience for the user and must also consider how the product integrates with the relevant adjacent systems. The application of Business Use Case and Product Use Case Scenarios will help in documenting the final decisions regarding the innovations and technological investments that will be made to improve the business, product or service.

    ReplyDelete
  3. Sukhpreet Singh23 April 2020 at 13:44

    Starting the solution – In this we bring the abstract of business into technological world of fulfillment.
    Iterative development – It doesn’t matter how you develop the software, but the invention of the real or actual needs of the solution by both you and your stakeholders is much important. To start the discovery of demand with abstract models and discussion instead of concrete implementations, it is more systematic in any event.
    Connections – People relate to each other through social media such as Facebook, Twitter, etc. because we love to be connected. One-third of the adults and more than half of teenagers are highly addicted to their smartphones. It is necessary that your product can easily connect with its hand holders, so that customers can get more information.

    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