Name: Muhammad Umar

Class: BSSE 5th (B)

Roll No: 8105
Subject: Software Requirement Engineering
Submitted by: Miss Ayesha Ayub
Riphah International University,
Faisalabad
Q#:1 Waterfall modes vs Scrum

Waterfall model:
Waterfall model was introduced by Royce in year 1970. Waterfall model follows the SDLC
approach and states that “ the phase are organized in a linear order and the output of one
phase becomes the input for the next phase.”

The waterfall model is a sequential (non-iterative) design process, used in software

development processes, in which progress is seen as flowing steadily downwards (like a
waterfall ) through the phase of conception, initiation analysis, design, construction, testing,
production/implementation and maintenance.

The sequential phases in Waterfall model are −

 Analysis
 Design.
 Coding
 Testing
 Implementation.
 Maintenance.

Advantages:

 Easy to manage due to the rigidity of the model – each phase has specific
deliverables and a review process.
 Simple and easy to understand and use.
 Phases are processed and completed one at a time.
 Works well for smaller projects where requirements are very well understood.

Disadvantages:

 It does not allow for much reflection or revision.

 No working software is produced until late during the life cycle.
 High amounts of risk and uncertainty.
 Not a good model for complex and object-oriented projects.
 Poor model for long and ongoing projects.

Scrum Methodology.
Scrum is a framework that helps teams work together.
Much like a rugby team (where it gets its name) training for the big game,
Scrum encourages teams to learn through experiences, self-organize while working on
a problem, and reflect on their wins and losses to continuously improve.

The Scrum methodology is defined by

 team roles,
 events (ceremonies)ggg
 Artifacts
 Rules.

Advantages:

 Scrum has more transparency and visibility than any other methodology.
 It increases the team accountability.
 Scrum is easy with changes. It accommodates changes.
 Scrum is a cost saving development methodology.

Disadvantages:
 Scrum need to be experienced and high-level persons, lack of experienced persons
scrum process has some risk of scope creep
 Scrum team requires experience and commitment team.
 Less experienced scrum master can ruin the whole process of development.
 If the task is defined poorly then the project can be lead to inaccuracies.

Q#:2 Requirement Engineering Process in Scrum?

Process of Scrum Model

Step 1. Product Backlog Creation

Product backlog is a list that consists of features that should be implemented during the
development process. It’s ordered by priority and its every item is called a User story.
Every user story gets a unique ID.
This list below shows how these stories can look like. These are actual product
requirements that were implemented during the XB Staff Manager Software developing
process.
Step 2. Sprint Planning and Sprint Backlog Creation
Firstly, you should determine what your sprint’s duration will be.
A short sprint allows you to release the working version of a product more frequently.
As a result, customer’s feedback will be received more often, and all the possible bugs
and errors will be revealed in time.

Step 3. Working on the Sprint. Scrum Meetings

After actual user stories for the current phase are chosen, the website development
process begins.
To track the current working process, a task board is commonly used. There are usually
big cards with the names of particular user stories and a bundle of little sticky notes with
a description of single tasks which are needed for implementation of this or that story.

Step 4. Testing and Product Demonstration

Since the ideal result of every sprint is a working product, the full life-cycle
testing process is very important.
There are different ways to minimize the costs of the testing period.
For example, you can decrease the overall amount of user stories. As a result, the
number of possible bugs will be minimized. The other way is to include QA engineers
into the scrum team.

Step 5. Retrospective and Next Sprint Planning

Retrospective’s main aim is to discuss the results and determine the ways how to
improve the development process on the next step.
The team should conclude what went well during the working process and what can be
done better during future iteration. When the ways of improvement are defined, the
team can concentrate on the next sprint planning.