Defining requirements for a SharePoint related project is a very important exercise. Seemingly small changes to the requirements can mean the difference between one with a low level of effort and one with a lot of customization and coding required. Project sponsors new to the platform may also have misconceptions about what can be done, or at least what can be done easily.
Paul Galvin recently posted his presentation from the SharePoint Best Practices session on Defining "Great" SharePoint Requirements.
Anyone with plans for future projects or implementations should check this out.
About Me
| Mike Oryszak Cary, NC, United States @next_connect |
 |
|
SharePoint Server MVP and SharePoint Consultant specializing in SharePoint Architecture and Development. I have been living in the Raleigh-Durham area since 1998 and have held a number of development and consulting positions servicing clients from a range of industries. My favorite SharePoint topic is social computing and how it can be used to increase team and cross-functional collaboration in the enterprise. In addition I enjoy listening to music and studying world history. | |
| |
No comments:
Post a Comment