Managing Requirements

in Scrum
Khuram Ali & Syed Ahsan
Scrum - an agile process
SCRUM is an agile, lightweight process for managing and controlling software
and product development in rapidly changing environments.
ions and impediments

A way to maximize prod

Iterative, incremental process
Team-based approach
developing systems/ products with rapidly changing requirements
Controls the chaos of conflicting interest and needs
Improve communication and maximize cooperation
Protecting the team form disrupt activity
2
 24 hours
Scrum-Overview Diagram

Sprint
2-4 weeks
Sprint goal
Return
Sprint
Potentially shippable
Cancel backlog
product increment
Coupons
Gift wrap Coupons
Product
3
backlog
Why do we need Requirements?
When 38 IT professionals in the UK were asked about which project stages
caused failure, respondents mentioned requirements definition more than any
other phase.

4
What are requirements?
A requirement is a statement about an intended product that specifies what it
should do or how it should perform.

Goal: To make as specific, unambiguous, and clear as possible.

5
What is Managing Requirements in Scrum
It's difficult to build a solution if you don't know the requirements.

3 types of requirement:

Business
Functional
Technical

6
What requirements should be managed?
Functional: What the product should do.

Data requirements: Capture the type, volatility, size/amount, persistence,

accuracy and the amounts of the required data.

Environmental requirements: a) context of use b) Social environment (e-g;

Collaboration and coordination) c) how good is user support likely to be d) what
technologies will it run on

User Requirements: Capture the characteristics of the intended user group.

Usability Requirement: Usability goals associated measures for a particular

7
How to manage Requirements in Scrum ***
o a systematic approach to eliciting, organizing, and documenting the requirements of the system,

o a process that establishes and maintains changing requirements.

o Important and helpful for real projects

Common problems
o No.1: Cant track change

o No.2: Difficult to write

o More

8
How to Manage changing requirements
Single channel of change control

Change Control Board (CCB).

Keep track history of requirements

Maintain version control

9
How to document requirements?
Requirement of description in scrum ****
o Natural language and graphical

o Widely accepted, consistent format

Use tools to help

o Software <IBM Rational RequisitePro>

o automating effective tool, template

10
What is a good REQUIREMENT ? ***
We must be able to modify an employees profile information
System should be easy to use
We should be able to enter the employee eye colour
The system should automatically be updated when the government changes
the law

11
4 Ws of Requirements in Scrum
Must have

Should have

Could have

Would have

12
Stakeholder MANAGEMENT
Must consider:
Management Support
Techniques
Terminologies
Keep it fun

13
Stakeholder MANAGEMENT

14
Breadth First APPROACH in Scrum
Requirement Management Techniques in Scrum
Interface prototype
CRC
UML
User Stories
CASE Tools

15
Interface PROTOTYPE
Collaborative approach for designing
interfaces

Just use post-its/slicky notes

16
CRC Cards

17
UML Modeling
Basic UML modeling that
customer understands

User roles and scenarios can be

modeled

18
User Stories

19
CASE Tools

20
Benefit Driven APPROACH

21
Scope Validation ***

22
Project Noise Level ***

23
24
25