SharePoint implementatie Howest
Download as PPTX, PDF0 likes539 views
The document discusses implementing and using SharePoint within an organization. It recommends setting goals and creating a roadmap before piloting SharePoint. Users should be trained repeatedly to change their mindset from thinking in terms of folders and documents to focusing on lists, columns, and workflows. Quick-win apps can be created through user-managed solutions or with Power User assistance. More advanced or custom apps may require development in Visual Studio or SharePoint Designer. Training should continue on-the-job through demonstration and collaboration on Quick-Win apps.
More Related Content
![[AIIM16] Don't Make Us Think: Getting SharePoint to Be Useful, Usable, and Used](https://cdn.slidesharecdn.com/ss_thumbnails/dontmakeusthink-160502162212-thumbnail.jpg?width=560&fit=bounds)
Similar to SharePoint implementatie Howest (20)
More from Gene Vangampelaere (20)
SharePoint implementatie Howest
- 1. IW Services Our mission is to help you uncover the information that remains largely hidden within your enterprise, and to help you exploit the resulting knowledge to the fullest so that you can improve performance within your organization.
- 2. Me o Gene Vangampelaere – SharePoint architect, University College Howest – Blogger: http://blog.spums.be – Twitter: http://twitter.com/vangampelaere – E-mail: [email protected]
- 3. Overview o Implementation o End users o Development
- 4. A successful implementation o Set your goals o Draw a roadmap o Pick some pilots o Train your users ...again… and again…
- 5. Goals o Implement an application framework o Enhance internal communication o Let teams collaborate (documents, calendars, tasks, …) o Exchange active data, o Introduce a unified way of work
- 6. Roadmap o Implement the organisation structure o Define your pilot(s) o Install and configure the framework o Rollout the structure o Setup the pilot(s) o Migrate central services o Implement teamsites for each team o … train users … train users …
- 7. End users: Think SharePoint Provide Publish and access manage Make Collaborate decisions Find Information Structure
- 8. Don’t think folders, think columns
- 9. Don't think documents, think lists and wikis
- 10. Don't think documents, think lists and wikis
- 11. Don't think documents, think lists and wikis
- 12. Don't think push, think pull
- 13. Don't think attachments, think links
- 14. Don't think mail, think workflows
- 15. Think SharePoint o Change of mindset – This takes time... o User adoption – ...and coaching
- 16. SharePoint Development o Quick-Win apps o Quick-Win apps (advanced) o Custom development
- 17. Quick-Win Apps o User managed solutions – Lists – Libraries – Views o Train the users first
- 18. Quick-Win Apps (advanced) o User managed solutions with SP Power User assistance – (connected) WebParts – SharePoint Designer (Free!) • Modify WebPart pages • JQuery (SPServices) • Workflows o RAD: Rapid Application Development
- 19. Custom development o Visual Studio – Create workflows – Create SPD workflow actions – Create WebParts – Consume the SP webservices o Takes more time “ If development is required, it’s because SharePoint cannot satisfy the organisations unique requirements “out of the box”, and something “custom” needs to be built. Custom development in SharePoint is regarded as the last resort, while an IT developer sees this as the first option, placing them in a situation they are not comfortable with right from the start.” http://nadirkamdar.blogspot.com/2010/08/why-there-is-shortage-of-sharepoint.htm
- 20. Examples o Holiday request application o ICT Helpdesk ticket system o Quality assurance dashboard o Jobs o And many, many quick-win apps!
- 21. Training o On the job o Click and show, create those Quick-Win apps together with the user o Train the IT department, they get a new role! o Howest: weekly consult session
- 22. More? o My blog: http://blog.SPums.be o Twitter: http://twitter.com/vangampelaere o http://NothingButSharePoint.com o SharePoint tweeps: http://twitter.com/vangampelaere/sharepoint
Editor's Notes
- #9: Folderswithunstructured data, manysubfolders, somewithhardlyany documentsTransfer to document libraries, with columnsRisk: simplyreplace folders by document libraries or sites and/or create folders within a libraryChooselibraries on the basis of requirements, functionalitiesGrouped view -> to make transitioneasier
- #10: While transferring documents from folders to document libraries, itbecomesobviousthatthere is analternative. Twoalternatives: lists andwikisExample of list:Each course generates 4 documents for each student. If there are 100 students we get 400 documents for each course. We can use a list with a few columns to replace this. You can extend the possibilities by using views on that list.A document is an isolated silo of information. You often have to open the document and browse it to view the content or structure. By using Wikipages we share the information in a clear way. It is very easy to link wikipages with each other or to generate an document index.lists: team meetingVoorbeeld wiki: dienst veiligheid.
- #11: While transferring documents from folders to document libraries, itbecomesobviousthatthere is analternative. Twoalternatives: lists andwikisExample of list:Each course generates 4 documents for each student. If there are 100 students we get 400 documents for each course. We can use a list with a few columns to replace this. You can extend the possibilities by using views on that list.A document is an isolated silo of information. You often have to open the document and browse it to view the content or structure. By using Wikipages we share the information in a clear way. It is very easy to link wikipages with each other or to generate an document index.lists: team meetingVoorbeeld wiki: dienst veiligheid.
- #12: While transferring documents from folders to document libraries, itbecomesobviousthatthere is analternative. Twoalternatives: lists andwikisExample of list:Each course generates 4 documents for each student. If there are 100 students we get 400 documents for each course. We can use a list with a few columns to replace this. You can extend the possibilities by using views on that list.A document is an isolated silo of information. You often have to open the document and browse it to view the content or structure. By using Wikipages we share the information in a clear way. It is very easy to link wikipages with each other or to generate an document index.lists: team meetingVoorbeeld wiki: dienst veiligheid.
- #13: Do not push the news intoeveryone’s mailbox. Let the users chose their own newssources.It’s like choosing between one fixed prepared menu or a self-service collect-and-go meal.Users can define a daily, weekly newsoverview or subscribe by RSS with their favorite RSS reader like Outlook.Example: weekly menu was mailed to all staff members, is now published as list and those interested can take subscription
- #14: Do not mail documents to each other’s mailbox.TIP: Share documents from Outlook to SharePoint: http://harmon.ie/TIP: Put the hyperlink behind some textTIP: shorten the hyperlink by using http://bit.ly or http://tinyurl.com or (internal) http://m.howest.beExample: presentations, send link not the powerpoint document.When you send the physical document, you lose ownership of that document. It creates storage issues with the receiving party.
- #15: Result: documents are generated without email traffic. The work is done by the workflow.