How to Best Develop Requirements for SharePoint Projects
2 likes4,605 views
The document discusses best practices for developing requirements for SharePoint projects. It emphasizes eliciting requirements through discussions with stakeholders to understand their needs rather than just gathering facts. It also stresses the importance of analyzing requirements to clarify them and ensure the proposed solution will meet the goals, rather than getting paralyzed by over-analysis. Requirements should then be documented in writing for validation.
How to Best Develop Requirements for SharePoint Projects
- 1. How to Best Develop Requirements for SharePoint Projects Video: h7p://youtu.be/__lsculdLNc Accessible content is available upon request.
- 4. E F F T Z
- 7. ©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. 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
- 9. 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
- 10. 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
- 11. 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
- 12. 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
- 13. 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
- 14. 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
- 15. 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
- 16. 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
- 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 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
- 19. 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
- 20. 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
- 21. 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
- 22. 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
- 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. 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
- 26. 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
- 27. 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
- 28. 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
- 30. Let’s Connect