4.
Session Objectives
 In this presentation, you will learn the best practices in developing
requirements for SharePoint projects
 In addition, you will be able to identify:
 Why having a well defined business case is necessary to effectively initiate
requirements gathering
 The key components of requirements gathering process
 Why requirements traceability is paramount in defining ROI in SharePoint
projects
Twitter: @meetdux Hashtag: #bpc10 #spreq

6.
How to Best Gather Requirements for SharePoint Projects
 What are Requirements?
 Eliciting is Not the Same as Gathering
 Analysis Doesn’t Lead to Paralysis
 Too Legit to Quit?
 Put it on Paper
 Summary
Twitter: @meetdux Hashtag: #bpc10 #spreq

9.
What is a Requirement?
 A requirement is something wanted or needed
 Formally documented and written statements
 Capabilities needed to solve a problem
 Conditions of a delivered system, services, product, or process
 Constraints on the system, service, product, or process
 Requirements are not
 Verbal, informal statements or conversations in the hallways
 Solutions that state how to solve the problem or meet the objectives
 Characteristics of other systems, services, products, or processes
 Project budgets, plans, or implementation details
Twitter: @meetdux Hashtag: #bpc10 #spreq

12.
Example: Defining a Business Need is a Must
 In a recent study, information workers today spend 45 mins/day searching for
information
 In a team of 20 people, that’s 900 mins/day
 In 3 months, that’s 54000 mins or about 37 person days
 How much does this cost in time & money?
 What if search productivity can be increased by 15%?
 That’s gaining 7 mins back from the 45 mins lost
Twitter: @meetdux Hashtag: #bpc10 #spreq

13.
Example: Mapping Needs to SharePoint Requirements
 Business requirements
 SharePoint shall increase user productivity by 15 percent
 User requirements
 The user shall be able to retrieve search results within five seconds of
submitting a search request that can support a maximum of 10,000
simultaneous search requests
 System requirements
 SharePoint server shall have two web front ends and a dedicated SQL
Server which has at least dual processors
Twitter: @meetdux Hashtag: #bpc10 #spreq

15.
How to Best Gather Requirements for SharePoint Projects
 What are Requirements?
 Eliciting is Not the Same as Gathering
 Analysis Doesn’t Lead to Paralysis
 Too Legit to Quit?
 Put it on Paper
 Summary
Twitter: @meetdux Hashtag: #bpc10 #spreq

16.
Requirements Elicitation
 Elicitation: gathering and understanding what stakeholders and users need
 Done at both an organizational (business) and a more detailed user level
 Elicitation is a human-based activity
 Determine requirements sources
 Decide how to gather information
 Involves research, reading, talking, and observing
 Business-level context and framework
 How the end users do their jobs
 What would help them do their jobs better
 Within the scope of our system, product, or process
Twitter: @meetdux Hashtag: #bpc10 #spreq

17.
BP
Elicitation Process
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?
Twitter: @meetdux Hashtag: #bpc10 #spreq

18.
Goal is to Identify Potential SharePoint Solution
 How would you like to drive a Lamborghini Diablo?
 BTW, you just learned how to ride a bike yesterday
Twitter: @meetdux Hashtag: #bpc10 #spreq

19.
How to Best Gather Requirements for SharePoint Projects
 What are Requirements?
 Eliciting is Not the Same as Gathering
 Analysis Doesn’t Lead to Paralysis
 Too Legit to Quit?
 Put it on Paper
 Summary
Twitter: @meetdux Hashtag: #bpc10 #spreq

23.
How to Best Gather Requirements for SharePoint Projects
 What are Requirements?
 Eliciting is Not the Same as Gathering
 Analysis Doesn’t Lead to Paralysis
 Too Legit to Quit?
 Put it on Paper
 Summary
Twitter: @meetdux Hashtag: #bpc10 #spreq

26.
How to Best Gather Requirements for SharePoint Projects
 What are Requirements?
 Eliciting is Not the Same as Gathering
 Analysis Doesn’t Lead to Paralysis
 Too Legit to Quit?
 Put it on Paper
 Summary
Twitter: @meetdux Hashtag: #bpc10 #spreq

31.
How to Best Gather Requirements for SharePoint Projects
 What are Requirements?
 Eliciting is Not the Same as Gathering
 Analysis Doesn’t Lead to Paralysis
 Too Legit to Quit?
 Put it on Paper
 Summary
Twitter: @meetdux Hashtag: #bpc10 #spreq