BLOG 2 (Pawandeep Kaur)
CHAPTER 2 – THE REQUIREMENTS PROCESS
What is Project Blastoff?
In the simple words the project Blastoff is a burst of activity to launch a requirements project. It assembles enough information to get your project off to a flying start and to ensure it is viable and well founded. In the Business requirement gathering there is an example for blastoff. So, they said just imagine launching a rocket. 10-9-8-7-6-5-4-3-2-1-blastoff! In addition to this in BRG blastoff is also known as “project initiation”, “kickoff”, “charter”, project launch and many other things.

Purpose of Project blastoff: the key purpose of project blastoff is to build the foundation for the requirement discovery that is to follow and to ensure that all the needed component for a successful project are in place. The principal stakeholders—the sponsor, the key users, the lead requirements analyst, technical and business experts, and other people who are crucial to the success of the project—gather together to arrive at a consensus on the crucial project issues.

Processes for requirements:  There are various kinds of processes for the requirements of the project which are listed below:
Ø Trawling the requirements
Ø Quick and Dirty Modeling
Ø Writing the Requirements
Ø Quality Gateway
Ø Reusing Requirements
Ø Reviewing the Requirements
Ø Iterative and Incremental Processes
Ø Requirements Retrospective
Ø Evolution of Requirements
Ø Formality Guide
I want to give some explanation for iterative and incremental processes and formality guide which I think important during the requirements of project.

Iterative and Incremental Processes: i want to share the diagram of these processes so that one can understand bitterly.


Formality Guide: formality guide is included to suggest where you might take a more relaxed approach to recording requirements, as well as those times when you should rightly be more systematic with your requirements discovery and communication. There are main three examples included in it.

Rabbit—small, fast, and short-lived. Rabbit projects are typically smaller projects with shorter lifetimes, where close stakeholder participation is possible. Rabbit projects usually include a lesser number of stakeholders.

Horse—fast, strong, and dependable. Horse projects are probably the most common corporate projects—they are the “halfway house” of formality.

Elephant—solid, strong, long life, and a long memory. An elephant project has a need for a complete requirements specification. If you are outsourcing the work, or if your organizational structure requires complete, written specifications, you’re an elephant

Comments

  1. Gagandeep KaurMarch 24, 2020 at 5:10 PM

    I want to talk about trawling for requirements. Trawling means discovering the requirements. After completion of project blastoff, business analysts focus on how is going work and what will their next step for business. Business analysts focus on what icebreaker technicians currently work do and their aspirations for work they hope to do. After understanding the meaning of work, business analysts and key stakeholders make a decision about which product is the best to improve the work.

    ReplyDelete
  2. ishikaMarch 26, 2020 at 2:22 PM

    There are the different methods of the modeling which is used at any time in the Volere life cycle and this can be shown as the " Prototype the Work". I want to talk about the one quick and the dirty way of the modelling technique which is mentioned here is Post-it notes. There are different notes which are used in the different ways and rapidly rearranged to show the different ways the work should be done. It is built on the white board to give the rapid visual explanation of the requirements that might be implemented to clarify the misunderstanding or missing the requirements.

    ReplyDelete
  3. Gurtej SinghMarch 26, 2020 at 8:07 PM

    I want to talk about Quality gateway for requirement. Basically,it means the Process in which all the requirements has been tested and normally it have a single point which make sure that every requirement must pass through before it can become a part of the specification. In this process, normally one or two people lead the role of tester and there are only authorized to pass requirements through gateway and every basic quality has been tested and ensure each requirement has a fit criterion attached to it before it reach its final stage.

    ReplyDelete

Post a Comment

Popular posts from this blog

Image
Chapter-1      Some Fundamental Truths What is the focus of Business Requirements Gathering?   A Business requirements elicitation (also known as Requirements Gathering or Capture) is the process of generating a list of requirements (functional, technical, etc.) from the different stakeholders that they will use as the basis of the requirement definition. This process is not that much easy because some of the stakeholders are not aware of the requirements required for the project. Business Problems and solutions ·        Cash and Resource Management : Business must capitalize and shore up cash reserve. ·        Monitoring Performance : Rounded with the performance indicators to provide the insights about the performing of the employees. ·        Technology: Be up to date in technique centre. ·        Customers Se...
Read more
Image
Chapter-5 Investigating the work   According to book information, investing the work means become known about the activities and actions while spending the portion of time which will increase the chances of making a positive impact on the business and it only become possible when you have deep understanding of process and then you able to do changes and generate new ideas when you need to do improvement in services on various stages of process. Trawling the business The word trawling means method of fishing with help of nets and similar actions are required in the business sector. In other words, individual able to stand at the stage where he or she know the way of catching every possible requirement and make the impossible things possible with the help of experience and trawling techniques. Trawling and business use cases The business use cases are the work's responses to the business events. These are studied until the analyst understands the desired functio...
Read more
Image
Blog 4 (Pawandeep Kaur) CHAPTER 4: Business Use Cases Business Event:   Business event also called business transactions. Any piece of work responds to things that happen outside it—it’s that simple. These happening called business event. Here I am giving an example of business event. : A business event happens at the moment the adjacent system decides to do something, or as part of its work some processing condition occurs. The adjacent system tells the work that the event has happened by sending a triggering data flow. When this stream of data arrives, the work responds by processing the incoming data, and by retrieving and recording stored data. Time-Triggered Business Events:   These events are initiated by the arrival of a predetermined time (or date).  There can be good example for understanding better like, your insurance company sends you a renewal notice a month before the anniversary of your policy.A business event takes place outside the scope of...
Read more