Time remaining:
Managing Projects and Requirements Gathering

Computer Science
Tutor: None Selected Time limit: 0 Hours

Imagine that you are a senior business analyst with a multinational corporation. Examine the process of requirements gathering.Suggest your strategy for gathering requirements from across divisional lines may encounter, and propose one method.

May 3rd, 2015

Step 1: Identify Key Stakeholders

Identify the key people who will be affected by the project. Start by clarifying exactly who the project's sponsor is. This may be an internal or external client. Either way, it is essential that you know who has the final say on what will be included in the project's scope, and what won't.

Then, identify who will use the solution, product, or service. These are your end-users. Your project is intended to meet their needs, so you must consider their inputs.

Step 2: Capture Stakeholder Requirements

Ask each of these key stakeholders, or groups of stakeholders, for their requirements from the new product or service. What do they want and expect from this project

Step 3: Categorize Requirements

To make analysis easier, consider grouping the requirements into these four categories:

  • Functional Requirements – These define how a product/service/solution should function from the end-user's perspective. They describe the features and functions with which the end-user will interact directly.
  • Operational Requirements – These define operations that must be carried out in the background to keep the product or process functioning over a period of time.
  • Technical Requirements – These define the technical issues that must be considered to successfully implement the process or create the product.
  • Transitional Requirements – These are the steps needed to implement the new product or process smoothly.

Step 4: Interpret and Record Requirements

Once you have gathered and categorized all of the requirements, determine which requirements are achievable, and how the system or product can deliver them.

To interpret the requirements, do the following:

  • Define requirements precisely – Ensure that the requirements are:
    • Not ambiguous or vague.
    • Clearly worded.
    • Sufficiently detailed so that everything is known. (Project over-runs and problems usually come from unknowns that were not identified, or sufficiently well-analyzed.)
    • Related to the business needs.
    • Listed in sufficient detail to create a working system or product design.

Step 5: Sign Off

Finally, make sure you get the signed agreement of key stakeholders, or representatives of key stakeholder groups, saying that the requirements as presented precisely reflect their needs.

May 4th, 2015

Studypool's Notebank makes it easy to buy and sell old notes, study guides, reviews, etc.
Click to visit
The Notebank
...
May 3rd, 2015
...
May 3rd, 2015
Dec 8th, 2016
check_circle
Mark as Final Answer
check_circle
Unmark as Final Answer
check_circle
Final Answer

Secure Information

Content will be erased after question is completed.

check_circle
Final Answer