nfr in scrum

21
Nothing Official Umm.. Functional about it Yashasree Barve 2012 September

Upload: yashasree

Post on 15-Jan-2015

497 views

Category:

Technology


0 download

DESCRIPTION

My draft presentation for discovering non functional requirements in Scrum Lifecycle

TRANSCRIPT

Page 1: NFR in Scrum

Nothing Official Umm.. Functional about it

Yashasree Barve

2012 September

Page 2: NFR in Scrum

What’s the Big Deal about Big Picture?

Image Source: http://en.wikipedia.org/wiki/File:Robin_shoots_with_sir_Guy_by_Louis_Rhead_1912.png

Page 3: NFR in Scrum

Problems?

• Scalability

• Reliability

• Security

• Supportability

Page 4: NFR in Scrum

Non Functional Requirement

A non-functional requirement is a requirement that specifies criteria that can be used to judge the operation of a system, rather than specific behaviors

• Qualities of System

• Quality Attributes

• Constraints?

Page 5: NFR in Scrum

Traditional Qualities

Page 6: NFR in Scrum

Modern Qualities

Page 7: NFR in Scrum

Why NFR in an Agile Conf?

Classic Dilemma of handling NFR in Scrum

Page 8: NFR in Scrum

User Story is all about Functionality

As a Sponsor

I want to Build a Low-Cost car

So that

Low Income Group can also enjoy

benefits of owning a four-wheeler

Page 9: NFR in Scrum

Release level NFRs

• infrastructure

• security

• availability

• reliability

• usability

• maintainability

• capacity

• recovery

Page 10: NFR in Scrum

Story level NFRs

• supportability

• security

• audit

• performance

• integrity

• usability

• maintainability

• compatibility

Page 11: NFR in Scrum

New Home for NFRs

• A New User Story

• Definition of Done

• Acceptance Criteria

Page 12: NFR in Scrum

Home # 1: A Separate User Story

As a Sponsor

I want to Build a Fuel Efficient car

So that

It gives a good mileage

As a Sponsor

I want to Build a Fuel Efficient car

So that

It gives at least 20 km/ltmileage

when driven in the city

Page 13: NFR in Scrum

Good Candidates for a separate user story

• Performance

• Availability

• Scalability

Page 14: NFR in Scrum

Home # 2: Definition of Done

• Accepted NFR story becomes a part of DoD

• Each page should render in less than a second

Page 15: NFR in Scrum

Which NFRs would be in DoD?

• Performance of a Website page

• Multiple Channel Access

• Audit

• Compatibility

• Analytics

Page 16: NFR in Scrum

Home # 3: Acceptance Criteria

• Security

• Only Administrator should have access to this page

Page 17: NFR in Scrum

Which NFRs would be in Acceptance Criteria?

• Social Features – Ability to like / comment

• Usability

o Responsive Design

• Performance

o Page should render in less than a second

o End to end transaction should be completed in 3 seconds

Page 18: NFR in Scrum

Cheat Sheet for NFRs

• Making NFR Testable

• Design Discussions every Sprint

• Involve Support groups

• Explore tools

• Radiators

• Regression tests

Page 19: NFR in Scrum

In Short

• Home for NFRs

• When should you talk about NFRs

• Things to Remember

Page 20: NFR in Scrum

Questions?

Page 21: NFR in Scrum

Thank You

Hope it helps!