Presented at ILTA Conference 2013

1. How to Develop
Quality Requirements for
SharePoint Projects
Dux Raymond Sy, PMP, MVP
Managing Partner, Innovative-e
@meetdux #misc6 #ilta13
Video Recording: https://www.youtube.com/watch?v=rPkMz6nyfAg

3. @meetdux #misc6 #ilta13
Hi, I’m Dux

6. @meetdux #misc6 #ilta13
What Are Requirements?
Something wanted or needed
Formally documented
Capabilities that solves a problem
Bounded by conditions and constraints

8. @meetdux #misc6 #ilta13
SharePoint is a
Business Platform

9. Business Needs First

10. @meetdux #misc6 #ilta13
4 Iterative Steps to Requirements
Development Success

12. Build Solutions, Don’t Showcase Features

13. @meetdux #misc6 #ilta13
Elicit != Gather
1. What do I need to know?
2. Where do I get this information?
3. Get the information
4. Organize what you know
5. Do I have enough information?

14. @meetdux #misc6 #ilta13
Example: Define Business Needs
How often does someone in finance have to
deal with collecting a bunch of project
expenses sent via e-mail with attached Excel
files regularly and consolidate it to a single
management report? How much time is spent
doing this?

15. @meetdux #misc6 #ilta13
Map Requirements
" Business requirements: SharePoint shall increase
Finance department’s productivity by 15%
" User requirements: The user shall be able to retrieve &
synchronize project expense information in SharePoint
from Excel without relying on email
" System requirements: Microsoft Excel shall be able to
sync information with a SharePoint site

17. @meetdux #misc6 #ilta13
Make Sense of It

18. @meetdux #misc6 #ilta13
Stated vs True Requirements
1. Profile Users
2. Model stated requirements
3. Gap analysis
4. Identify the real requirements

19. @meetdux #misc6 #ilta13
Example: Process Flow

21. @meetdux #misc6 #ilta13
IT, Can You Handle This?

22. @meetdux #misc6 #ilta13
Confirm and Prioritize

24. @meetdux #misc6 #ilta13
Generate Requirements
Document
" Formally communicates
" Overall quantitative and qualitative characteristics
" Functionality of the desired end result or outcome
" Should include
" Requirement Statements
" Process Diagrams
" Traceability Matrix

25. @meetdux #misc6 #ilta13
Tip: Writing Requirements
" <Subject> shall be able to <capability> within
<criterion>
" <Subject> shall be able to <capability>
" Where criterion is assumed to be 100 percent of the stated
capability

26. @meetdux #misc6 #ilta13
Example Requirements
" Business requirements: SharePoint shall increase
Finance department’s productivity by 15%
" User requirements: The user shall be able to retrieve &
synchronize project expense information in SharePoint
from Excel without relying on email
" System requirements: Microsoft Excel shall be able to
sync information with a SharePoint site

27. @meetdux #misc6 #ilta13
4 Iterative Steps to Requirements
Development Success

28. e: dux.sy@innovative-e.com
t: http://twitter.com/meetdux
w: http://innovative-e.com

29. Thank You!