As most would agree, one of the main factors that can lead to a failed SharePoint implementation is the lack of proper requirements gathering.
As most would agree, one of the main factors that can lead to a failed SharePoint implementation is the lack of proper requirements gathering. I’ve discussed this in a previous blog post and made a case on why upfront investment on proper requirements gathering is critical.
As most would agree, one of the main factors that can lead to a failed SharePoint implementation is the lack of proper requirements gathering. I’ve discussed this in a previous blog post and made a case on why upfront investment on proper requirements gathering is critical.
I had the opportunity to present “Best Practices in Gathering Requirements for SharePoint Projects” at the Baltimore SharePoint Users’ Group 2nd Anniversary last June 18, 2009. Here are the tweets during that evening and also the recorded livestream.
In the presentation, I shared practical techniques in gathering requirements for SharePoint Projects. In addition, I explained the key components of requirements gathering process: Elicit, Analyze, Validate and Document.
As promised, here are resources from the presentation:
– Slide Deck
– Requirements and Project Management Templates
– Books:
1. More About Software Requirements: Thorny Issues and Practical Advice
– Slide Deck
– Requirements and Project Management Templates
– Books:
1. More About Software Requirements: Thorny Issues and Practical Advice
Lastly, here is the 74 minute recorded screencast from the presentation that evening. Enjoy!
