Access Millions of academic & study documents

Waterfall Vs. Scrum Requirements Process

Content type
User Generated
Subject
Computer Science
Type
Homework
Showing Page:
1/4
Running Head: WATERFALL VS. SCRUM REQUIREMENTS PROCESS 1
Waterfall vs. Scrum framework requirements process
Name;
Course:
Institution:
Date:

Sign up to view the full document!

lock_open Sign Up
Showing Page:
2/4
WATERFALL VS. SCRUM REQUIREMENTS PROCESS 2
Waterfall vs. Scrum framework requirements process
Software requirements are a subset of software engineering that handles the
establishment of the stakeholder needs. These requirements define the problem that the software
is solving. Requirements are the conditions or capabilities that the user needs to provide a
solution to the problem (IEEE Computer Society, 1990). The approaches to software
development have been evolving with company cultures. The frequent change in the customer
needs has made the traditional software development Life cycles more and more obsolete while
giving birth to new, dynamic approaches like the scrum framework. There exists a strong
contrast between the traditional SDLC and the Scrum methodologies as described below.
Waterfall software development is a traditional approach to software development that
consists of linearly sequential separate phases (Limaye, 2009). For a phase to commence the
previous phase must be complete, the product of one phase is the input to the following phase.
Each phase of the development process only takes place once in the development lifecycle.
Requirement collection and analysis forms the first phase of this approach. In this phase, all the
possible system requirements are captured and documented in the requirement specification
document. This approach gives no room for the incorporation of any change to the development
process that was not prior seen (Limaye, 2009). A variation in the requirements will mean a
clean start on the entire development process.
On the other hand, Scrum framework provides a flexible software requirement generating
process (Maurer & Wells, 2003). In this process, the software requirements are gathered through
user stories. User stories are agile software development tool that captures a description of a
software feature from the viewpoint of the end user. It is a short and precise description of a
function by the person desiring the new capability (Maurer & Wells, 2003). It aids in the creation

Sign up to view the full document!

lock_open Sign Up
Showing Page:
3/4

Sign up to view the full document!

lock_open Sign Up
End of Preview - Want to read all 4 pages?
Access Now
Unformatted Attachment Preview
Running Head: WATERFALL VS. SCRUM REQUIREMENTS PROCESS Waterfall vs. Scrum framework requirements process Name; Course: Institution: Date: 1 WATERFALL VS. SCRUM REQUIREMENTS PROCESS 2 Waterfall vs. Scrum framework requirements process Software requirements are a subset of software engineering that handles the establishment of the stakeholder needs. These requirements define the problem that the software is solving. Requirements are the conditions or capabilities that the user needs to provide a solution to the problem (IEEE Computer Society, 1990). The approaches to software development have been evolving with company cultures. The frequent change in the customer needs has made the traditional software development Life cycles more and more obsolete while giving birth to new, dynamic approaches like the scrum framework. There exists a strong contrast between the traditional SDLC and the Scrum methodologies as described below. Waterfall software development is a traditional approach to software development that consists of linearly sequential separate phases (Limaye, 2009). For a phase to commence the previous phase must be complete, the product of one phase is the input to ...
Purchase document to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.
Studypool
4.7
Indeed
4.5
Sitejabber
4.4