why do we need to gather requirements
Project Requirements Requirements are the backbone of any project. P They help us understand the needs of our users and help us provide a solution to meet those needs. P Documented requirements provide information not only to the design team but also to the testing team and other project stakeholders. P For example, Project Managers need to be able to estimatePtime lines, determine resources required, and manage budgets. Clients and customers need to be aware of changes that impact users, processes, and help files. Also, vendors can use requirements to help provide accurate quotes for their products and services. ItPdoesn tPmatter if you are working in a Traditional or Agile world, all stakeholders use the requirements in different ways but they should all get their requirements from a single source. P Multiple sources of information can lead toPmisunderstandingsPor data being out of sync. P Traditionally this single source is the Business Requirements Document (BRD) or in an Agile world it is the Product Backlog (PD). Requirements should be traced through the life cycle of a project with a unique identifier. P The quality of the information in the requirements document (BRD or PD) is key to the success of any project. P Other than the delivered product, it is the single most important deliverable of a project. Design Requirements The requirements document is used to create the physical design and user interfaces. P It helps develop the functional and non-functional specifications, the business, security, and performance rules.
If the rules are undefined or hard to understand then the designers will have to fill in the requirements gaps. P This could lead to missed requirements, scope creep, and rework. Providing quality requirements early in the design phase can help deliver a better product, as a single missing requirement may result in one or more features missingPfromPthe product and the cost to add or fix requirements increase dramatically later in the traditional development life cycle. Testing Requirements Testing is not just a phase that happens before you deliver the product. Test planning should be a part of the requirements gathering process. The BA should always be thinking How can I test this requirement? P Every requirementPshouldPbe tested and there should be a test for every requirement. The requirements document should be used early in the project to help testers create the test plan and test cases, help setup the test environments, determine staffing and training, determine what test Data should be created, and select the automated and manual tests that should bePexecuted. Quality documentation is important and the requirements doucment is no exception. P Requirements are used by a number of stakeholders for a number of reasons but with one goal in mind; to produce the best product at the best value. P If something is worth doing then it is worth documenting. P Remember why we need to document requirements the next time you are working on a project.
It's difficult to build a solution if you don't know the requirements (in spite of the fact that many teams still try to do it today).
The "elicitation" step is where the requirements are first gathered from the client. Many techniques are available for gathering requirements. Each has value in certain circumstances, and in many cases, you need multiple techniques to gain a complete picture from a diverse set of clients and stakeholders. Here's a look at some of the approaches you can take. Note: This information is also available as a. The most common technique for gathering requirements is to sit down with the clients and ask them what they need. The discussion should be planned out ahead of time based on the type of requirements you're looking for. There are many good ways to plan the interview, but generally you want to ask open-ended questions to get the interviewee to start talking and then ask probing questions to uncover requirements. Group interviews are similar to the one-on-one interview, except that more than one person is being interviewed в usually two to four. These interviews work well when everyone is at the same level or has the same role. Group interviews require more preparation and more formality to get the information you want from all the participants. You can uncover a richer set of requirements in a shorter period of time if you can keep the group focused.
In a facilitated session, you bring a larger group (five or more) together for a common purpose. In this case, you are trying to gather a set of common requirements from the group in a faster manner than if you were to interview each of them separately. JAD sessions are similar to general facilitated sessions. However, the group typically stays in the session until the session objectives are completed. For a requirements JAD session, the participants stay in session until a complete set of requirements is documented and agreed to. Questionnaires are much more informal, and they are good tools to gather requirements from stakeholders in remote locations or those who will have only minor input into the overall requirements. Questionnaires can also be used when you have to gather input from dozens, hundreds, or thousands of people. Prototyping is a relatively modern technique for gathering requirements. In this approach, you gather preliminary requirements that you use to build an initial version of the solution в a prototype. You show this to the client, who then gives you additional requirements. You change the application and cycle around with the client again. This repetitive process continues until the product meets the critical mass of business needs or for an agreed number of iterations. Use cases are basically stories that describe how discrete processes work. The stories include people (actors) and describe how the solution works from a user perspective.
Use cases may be easier for the users to articulate, although the use cases may need to be distilled later into the more specific detailed requirements. This technique is especially helpful when gathering information on current processes. You may find, for instance, that some people have their work routine down to such a habit that they have a hard time explaining what they do or why. You may need to watch them perform their job before you can understand the entire picture. In some cases, you might also want to participate in the actual work process to get a hands-on feel for how the business function works today. If you are a vendor, you may receive requirements through an RFP. This list of requirements is there for you to compare against your own capabilities to determine how close a match you are to the client's needs. On some projects, the requirements are not "uncovered" as much as they are "discovered. " In other words, the solution is brand new and needs to be created as a set of ideas that people can agree to. In this type of project, simple brainstorming may be the starting point. The appropriate subject matter experts get into a room and start creatively brainstorming what the solution might look like. After all the ideas are generated, the participants prioritize the ones they think are the best for this solution. The resulting consensus of best ideas is used for the initial requirements.
- Views: 110
why do we need network management system
why do we carry out risk assessments
why do organizations have written policies and procedures
why do people make open source software
why should i hire you interview question and answer
why do you want to become a supervisor
why do we need database management system