This document discusses how non-functional requirements (NFRs) can be addressed in agile development frameworks like Scrum. It proposes three homes for NFRs: 1) creating a separate user story to define NFRs like performance and availability, 2) including important NFRs in the definition of done, and 3) specifying NFRs like security and usability as acceptance criteria. It also provides examples of NFRs that would fit into each home and recommends discussing NFRs regularly, involving support groups, and using tools to test NFRs.

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

2. 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

3. Problems?
• Scalability
• Reliability
• Security
• Supportability

4. 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?

5. Traditional Qualities

6. Modern Qualities

7. Why NFR in an Agile Conf?
Classic Dilemma of handling NFR in Scrum

8. 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

9. Release level NFRs
• infrastructure
• security
• availability
• reliability
• usability
• maintainability
• capacity
• recovery

10. Story level NFRs
• supportability
• security
• audit
• performance
• integrity
• usability
• maintainability
• compatibility

11. New Home for NFRs
• A New User Story
• Definition of Done
• Acceptance Criteria

12. Home # 1: A Separate User Story
As a Sponsor
I want to
Build a Fuel Efficient car As a Sponsor
So that I want to
Build a Fuel Efficient car
It gives a good mileage
So that
It gives at least 20 km/lt
mileage
when driven in the city

13. Good Candidates for a separate user story
• Performance
• Availability
• Scalability

14. Home # 2: Definition of Done
• Accepted NFR story becomes a part of DoD
• Each page should render in less than a second

15. Which NFRs would be in DoD?
• Performance of a Website page
• Multiple Channel Access
• Audit
• Compatibility
• Analytics

16. Home # 3: Acceptance Criteria
• Security
• Only Administrator should have access to this
page

17. 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

18. Cheat Sheet for NFRs
• Making NFR Testable
• Design Discussions every Sprint
• Involve Support groups
• Explore tools
• Radiators
• Regression tests

19. In Short
• Home for NFRs
• When should you talk about NFRs
• Things to Remember

20. Questions?

21. Thank You
Hope it helps!