Getting good requirements for a SharePoint project is in some ways more critical than for a project that’s based on more widely understood technologies. The fact that SharePoint isn’t widely understood by clients — whether internal or external — means the potential for misunderstandings is much greater. For this reason, it’s more critical to discuss each feature of SharePoint to understand of how the feature works out-of-the-box and to understand how the organization envisions those features. Whether you choose to design and architect your SharePoint technologies solution yourself or decide to work with an outside partner to perform the architecture and design steps, you’ll find that having a foundation in solid requirements makes the development process run smoother and results in a better solution for your business needs.
http://my.advisor.com/doc/16797 [Article removed from the website]
Dear Mr Bogue,
Thank you for putting up such an awesome blog. Your experience and insights have been of tremendous value. I’m really hoping that you keep a copy of all of your blogs because the one for this article (https://thorprojects.com/2023/blog/archive/2005/09/03/how-to-gather-windows-sharepoint-services-requirements.aspx) points to a parked domain. I would be ever so grateful if you could send me this article via email or kindly point me to another URL where I can find your in-depth article on requirements gathering for Sharepoint projects
Sorry about that. They took that domain offline, I’ve corrected the link.