Your SlideShare is downloading. ×

How to Best Develop Requirements for SharePoint Projects

2,252

Published on

Presented at SharePoint Saturday Honolulu 2014

Presented at SharePoint Saturday Honolulu 2014

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,252
On Slideshare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
40
Comments
0
Likes
3
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. How to Best Develop Requirements for
 SharePoint Projects   Video:  h7p://youtu.be/__lsculdLNc     Accessible  content  is  available  upon  request.      
  • 2. E F F T Z
  • 3. ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 4. How to Best Develop Requirements •  •  •  •  •  What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 5. Requirements are … ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 6. Requirements Focus ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 7. Defining Business Need is a Must ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 8. Mapping Requirements ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 9. How Do You Develop Requirements? ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 10. How to Best Develop Requirements •  •  •  •  •  What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 11. Elicitation Process ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 12. Goal is to Build Solutions ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 13. How to Best Develop Requirements •  •  •  •  •  What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 14. What is Requirements Analysis? ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 15. Analysis Process ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 16. Example: Process Flow Diagram ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 17. How to Best Develop Requirements •  •  •  •  •  What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 18. What is Requirements Validation? ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 19. How to Best Develop Requirements •  •  •  •  •  What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 20. Generate a Requirements Document ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 21. Writing Requirements ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 22. Mapping Requirements ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 23. How to Best Develop Requirements •  •  •  •  •  What are Requirements? Eliciting is Not the Same as Gathering Analysis Doesn’t Lead to Paralysis Too Legit to Quit? Put it on Paper ©AvePoint,  Inc.  All  rights  reserved.  ConfidenDal  and  proprietary  informaDon  of  AvePoint,  Inc.  No  part  of  this  may  be  reproduced,  stored  in  a  retrieval   system,  or  transmi7ed  in  any  form  or  by  any  means,  without  the  prior  wri7en  consent  of  AvePoint,  Inc.   spshnl @meetdux
  • 24. Ahsante thank you
  • 25. Let’s Connect  

×