How to Best Develop Requirements for SharePoint Projects

3,099
-1

Published on

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
3,099
On Slideshare
0
From Embeds
0
Number of Embeds
14
Actions
Shares
0
Downloads
43
Comments
0
Likes
3
Embeds 0
No embeds

No notes for slide

How to Best Develop Requirements for SharePoint Projects

  1. 1. How to Best Develop Requirements for
 SharePoint Projects   Video:  h7p://youtu.be/__lsculdLNc     Accessible  content  is  available  upon  request.      
  2. 2. E F F T Z
  3. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 24. Ahsante thank you
  25. 25. Let’s Connect  

×