Projects are developed according to a set of requirements. Often there are many explicit requirements. And usually those represent only a tip of the iceberg. There are also hidden requirements: implicit and/or unknown requirements. And some of hidden requirements are important. Not recognizing important requirements in time leads to not good consequences. This talk is about common categories of hidden requirements that are often missed only to be discovered a bit too late.

1. JULY 14TH
TED ROGERS SCHOOL OF MANAGEMENT,
RYERSON UNIVERSITY
ProductCamp
2018
productcamptoronto.ca

2. Hidden Requirements
pngtree.com
 Explicit Requirements
 Implicit Requirements
 Expectations
 Unknown Requirements

3. Examples:
No internet connection
Incorrect user input
Payment rejection due to insufficient
funds
Any other error
Unhappy Paths

4. Examples:
New account with nothing to display
No items found in search
Online shop has unexpectedly large
amount of items
Edge/Corner Cases

5. Examples:
New way of paying is added but
transaction history needs to be updated
as well
Annotating images is too cumbersome
on devices with small screens, and
might be worth disabling it there
Unaccounted Interactions

6. Examples:
Advanced accessibility
Corporate devices all have large
screens, thus small screen support may
be skipped
User language specifics
Target Audience Specifics

7. Examples:
Future extensibility
High bus factor
Ability to change development team
Use of specific tools
Use of specific methodologies
Meta Requirements

8. Roman Temchenko
Reliabe Dev Founder
www.reliabledev.org
temchenko.r@gmail.com
Thank You!