In this session you will learn how to translate business requirements into usable SharePoint
…

In this session you will learn how to translate business requirements into usable SharePoint
specifications? How to accurately plan effort and scope for a SharePoint project?
How to prepare a clear, complete and concise document for the development team? If these
questions keep you up at night this session is for you!

The following topics will be covered during this presentation:
 Requirements Definition
 Information Architecture
 Functional, and
 Non-Functional Specifications

Analysis templates used in the presentation will be distributed to attendees.

5.
Part A
Requirements definition
Focus first on the ''What''?
“The value of an idea lies in the using of it.”
- Thomas A. Edison
SharePoint Functionnal Analysis | 5

6.
1
Define requirements
Do you know the difference between?
Business analyst
Understand business process
Read documentation if exists
And
Functional analyst
Understand SharePoint mechanisms
Knows possibilities with SharePoint
and transcribe them to functional
questions.
Identify super users or product
owners
Link between IT and business
Identify actual problems on process
or current solution
Product owner(s) best friend
Animate workshops
SharePoint Functionnal Analysis | 6

7.
1
Define requirements
By writing a backlog
Very first document
Identify what will be done in your project
Don’t neglect it
Used with agile methodologies
Sprintable and releasable (ex SCRUM)
Prioritized
Flexible
Requirements as stories
• Independent analysis on each
This document can be
A simple flat list
• Avoid TFS…
A map (?!?)
SharePoint Functionnal Analysis | 7

9.
1
Define requirements – Tools & Techniques
User Story Mapping
Concept
Impacts
Business goals
Why you do it?
Is there any constraints (IT,
functional, human..) on?
Actors/Profiles
Who will use it?
Activities
User stories
User workflow
What are their responsibilities on it?
What are their tasks within those
responsibilities?
SharePoint Functionnal Analysis | 9

12.
1
Define requirements – Tools & Techniques
User Story Mapping
Summary
 Live in a dream, don’t talk about SharePoint capabilities
Everything is possible here !
 Focus on roles and responsabilites
Who can do what in the system? This, is governance.
 Focus on requirements, not solutions
No more: « I want a search engine » or « I want a SharePoint list with five columns »
 Reveal information flows
That they will help you in the future to design your information architecture
 Super effective but sometimes hard to assimilate
Practice, practice and practice. Dont be afraid to try. All you need is listening and rigor.
SharePoint Functionnal Analysis | 12

15.
2
Prioritize requirements
Why prioritize?
You have to start with something
« I want it all » is not a valid response
Agile development guideline
First deliver features that give you the most
value
Source: http://innovationgames.com
SharePoint Functionnal Analysis | 15

20.
B
Functional analysis
With SharePoint
Top SharePoint analysis facts
1 Analy…what??
SharePoint is like Legos®, you can do anything, for better for worse.
It’s up to you to choose the right brick for the right use
2 The SharePoint trap: when the means
condition the needs
Tell me what SharePoint can do, I will tell you what you need…
3 Solutions are not close enough to users day
to day needs
IT department is not often the best resource to determine whole
user requirements…
SharePoint Functionnal Analysis | 20

28.
4
Effectively storing information
How should data be stored within a requirement?
Data distribution criteria
Volume
• What is the amount of data?
Information security
• Who need to access these data?
Business context
• Does the structure have to follow a
business hierarchy?
SharePoint Functionnal Analysis | 28

39.
7
Define the conditions for information recovery
Under which conditions should information should
appear in the page?
Are the recovered items have to correspond to reality at time T in
SharePoint?
Is there a sort needed on the elements?
Are there any hierarchical constraints between elements?
Are there any relationships between entities?
Are these items must be targeted to a specific audience?
Are there multilingual constraints?
Must queries be reused?
Are there conditional constraints on queries?
What is the Information life cycle?
SharePoint Functionnal Analysis | 39

40.
8
Define relational behaviors
What are the relational constraints on the
information?
Notions of filtering and connections in
response to actions
Ex: An user select an item in a list  an
other value is selected in a other
component.
Ex: Language on the page has changed
SharePoint Functionnal Analysis | 40

44.
B
Methodology summary
Your functional analysis with SharePoint
1
What does the requirement look like?
2
What are the information types?
3
What are the relationships?
4
Where data is stored?
5
What are the data flows?
6
What are the page types?
7
What are the display constraints?
8
What are the behaviors on pages?
9
How information are displayed?
SharePoint Functionnal Analysis | 44