share point customizations how far should you go
DESCRIPTION
This presentation was given by Alexander Meijers as part of the Sparked Toolkit Session: SharePoint Nightmares. It discusses the boundaries of SharePoint when it comes to customizations.TRANSCRIPT
![Page 1: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/1.jpg)
SHAREPOINT CUSTOMIZATIONS
How far should you go?
![Page 2: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/2.jpg)
Do you recognize yourself? Yes, we are building everything our
selves! We are deviating from the standards We say too often “SharePoint? Yes it
can!” We have complicated the design
![Page 3: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/3.jpg)
Reality check!
Not delivering what the customer asked
Too complicated system Performance issues Over budget SharePoint gets a bad name
Know the product its limits!
![Page 4: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/4.jpg)
![Page 5: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/5.jpg)
First step to disaster
Communication Lack of it Assumptions No documentation
• Lesson learned Communicate!! It is not that hard! Document everything Say NO to your customer Customer sessions
![Page 6: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/6.jpg)
Second step to disaster
The data model Over designed the system Based on relational databases Mapped to Content Types and Lists Multi-tier solution implementation
• Lessons learned Do not threat Lists as a database table Check if you need to store the data in
SharePoint or another location Do I really need all those tiers? Keep it stupid simple
![Page 7: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/7.jpg)
Third step to disaster
Implementation Only focus on the presentation and not on
maintaining the content Not using out-of-the box functionality Developers only know their piece No code documentation
• Lessons learned Try to use as much as possible out-of-the box Think of Content management, Security and
Search from the beginning Document your code
![Page 8: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/8.jpg)
Fourth step to disaster
Everything else Migration? No, lets wait till we finish the
Portal Not cooperation with the other parties
• Lessons learned Do NOT under estimate migration Be a team for the customer! We are one!
There is no you!
![Page 9: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/9.jpg)
My information
Twitter: http://www.twitter.com/ameijersBlog:
http://www.bloggix.com/blogs/microsoftUser group: http://www.dutchsug.nl Linkedin:
www.linkedin.com/in/alexandermeijers
![Page 10: Share Point Customizations How Far Should You Go](https://reader035.vdocuments.us/reader035/viewer/2022081907/54b7b1334a795939708b45a1/html5/thumbnails/10.jpg)
Questions?