1 / 10

Collaborative Construction of Custom SharePoint Artefacts

Collaborative Construction of Custom SharePoint Artefacts. Gavin Barron. About Me. Gavin SharePoint Certified Rocket Scientist - development (MCTS MOSS & WSS) http://gavinb.net gavinb@intergen.co.nz. Session Overview. Approaches to software development.

mercury
Download Presentation

Collaborative Construction of Custom SharePoint Artefacts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Collaborative Construction of Custom SharePoint Artefacts Gavin Barron

  2. About Me Gavin SharePoint Certified Rocket Scientist - development (MCTS MOSS & WSS) http://gavinb.net gavinb@intergen.co.nz

  3. Session Overview • Approaches to software development. • Creation of SharePoint artifacts in the real world. • The Ugly. • The Bad. • The Good. • Application of software development practices.

  4. Approaches to software development. • Traditional Waterfall Approach. • Familiar • ‘Proven’ • Great for forecasting expenditure. • Agile • Requires heavy customer buy-in • Able to respond to changing needs more easily • Helps to ensure that users get what they want.

  5. Creation of SharePoint artifacts – The Ugly • Single SharePoint server for the entire organisation. • Most users are ‘designers’. • No processes or policies to control user actions. • Meta-Data is not constructed using Content Types. • No ‘owner’ for content. • Chaos!

  6. Creation of SharePoint artifacts – The Bad • Requirements for meta-data captured ONLY in documentation. • Overbearing change management. • Developers hand craft artefacts with no user involvement. • Chasing a fully automated system regardless of cost. • Slow to react to business needs.

  7. Creation of SharePoint artifacts – The Good • Separate servers for Dev, Test & Prod. • Interactive requirements gathering. • Developers utilise artefacts created in requirements phase. • Pragmatic use of technology versus people. • Sensible application of change management. • Rapid reaction to business needs.

  8. Application of software development practices. Demo

  9. Useful links. • VSeWSS 1.2 http://www.microsoft.com/downloads/details.aspx?FamilyID=7bf65b28-06e2-4e87-9bad-086e32185e68&displaylang=en • VSeWSS User Guide http://www.microsoft.com/downloads/details.aspx?FamilyId=A8A4E775-074D-4451-BE39-459921F79787&displaylang=en • Andrew Connell’s STSADM Extensions http://www.andrewconnell.com/blog/articles/MossStsadmWcmCommands.aspx • Gav’s Blog http://gavinb.net

More Related