Rik Dekker       Cas van IerselPitfalls and Success Factors of an    Office 365 Implementation
Agenda•  Our Office 365 experience  –  Project  –  Approach  –  Deployment•  The development challenges  –  OOTB quick win...
What is Office 365?Online Versions of Microsoft Software             in the Cloud
Licenses•  Office 365 for professionals and small   businesses (Plan P)•  Office 365 for midsize businesses and   enterpri...
The project•  Large Office 365 implementation  –  4500 users (of which 3000 kiosk users)  –  Social intranet  Personal lan...
Why Office 365 for this project?•  Different type of users     –  Single Sign On with AD sync•    High availability•    No...
Biggest succes factor•  Microsoft takes care of IT  –  Updates     •  Hotfixes, Service Packs  –  Upgrades     •  New func...
The approach•  Agile (7 sprints)  –  Product backlog  Per sprint  –  Stayed as close as possible to OOTB     •  Configurat...
The team•  Product owner•  Project manager customer•  Developer  –  NL and India•  Designer•  Architect/team lead•  Projec...
Tools•  Visual Studio  –  Powerfull tool for developers  –  Only sandboxed solutions for Office365  Development takes more...
DTAP environment•  Local development machine•  Test in the cloud•  Acceptance/Production in the cloud Risk for early adopt...
Deployment•  Same deliverables as ‘normal’ SP project  –  Web parts  –  Page layouts  –  Master pages  –  WSP’s  –  Docume...
Deployment challenges•  How to deploy the site structure?Normal way of deployment not possible:•  No PowerShell•  No conso...
Deployment solutionOptions:•  Site templates•  Migration tools  –  Different tools available Tool together with Web templ...
Lessons learned•  Some 3d party tools not usable•  Rapid development with the right tools•  Limitations of Sandbox asks fo...
SummaryWith Office365 you can create powerfullsolutions like on premise. You just needsome more creativity
The development   challenges
DevelopmentFirst challenge: Aggregation(How may SiteCollections do I need?)
DEMO: How to extend the CQWP to fit your                needs
Aggregation•  OOTB aggregation•  Easy to configure•  Easy to brand
AggregationWhat to do with aggregation over multiple            Site Collections?
DEMO: Configure Search to fetch cross-        sitecollection data
AggregationAnother cool way of getting data!
DEMO: Configure CQWP + RSS to fetch      cross-sitecollection data
Sandboxed SolutionAbout Sandboxed Solutions..              Farm         Webapplication         Site Collection            ...
Sandboxed Solution(#seats × 200) + 300
Sandboxed Solution AbnormalProcessTerminationCount        CPUExecutionTime      CriticalExceptionCount          Invocation...
Sandboxed Solution•  Deployment•  Limited but Powerful•  Resource Points System•  SiteCollection context only
Client Object ModelFinding the Balance with COM     (Client Object Model)
DEMO: Sandboxed WebPart with CSOM
Client Object Model   About COM …
Client Object Model No Resource Points Possibilities same as sandboxed•  More code•  Tools less mature then VS
DEMO: All put together, real world SP          Online example
SummaryWith Office365 you can create powerfullsolutions like on premise. You just needsome more creativity!
Questions?Resources•  http://msdn.microsoft.com/en-us/library/gg615462.aspx•  http://community.office365.com/en-us/f/145/t...
SharePoint Connections Conference Amsterdam - Pitfalls and success factors of an office 365 implementation - Cas van Ierse...
SharePoint Connections Conference Amsterdam - Pitfalls and success factors of an office 365 implementation - Cas van Ierse...
SharePoint Connections Conference Amsterdam - Pitfalls and success factors of an office 365 implementation - Cas van Ierse...
Upcoming SlideShare
Loading in …5
×

SharePoint Connections Conference Amsterdam - Pitfalls and success factors of an office 365 implementation - Cas van Iersel - Rik Dekker

1,241 views

Published on

Valkuilen en successen binnen een implementatie van Office 365, SharePoint, Exchange en Lync Online in de Cloud. 4000 seats binnen Zorg - Health. Intramurele en extramurele medewerkers hebben samen een digitale werkomgeving. Het Nieuwe Werken voor een thuiszorginstelling.

Published in: Business, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,241
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
15
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

SharePoint Connections Conference Amsterdam - Pitfalls and success factors of an office 365 implementation - Cas van Iersel - Rik Dekker

  1. 1. Rik Dekker Cas van IerselPitfalls and Success Factors of an Office 365 Implementation
  2. 2. Agenda•  Our Office 365 experience –  Project –  Approach –  Deployment•  The development challenges –  OOTB quick wins –  Sandbox troubles –  Power of the Client
  3. 3. What is Office 365?Online Versions of Microsoft Software in the Cloud
  4. 4. Licenses•  Office 365 for professionals and small businesses (Plan P)•  Office 365 for midsize businesses and enterprises –  Kiosk worker (Plan K family) –  Information worker (Plan E family)
  5. 5. The project•  Large Office 365 implementation –  4500 users (of which 3000 kiosk users) –  Social intranet Personal landingspage Aggregated news Aggregated discussions My colleagues per Workflows Forms department Collaboration portal Personalised actions Last changed / important documents Respond Support mobile devices View documents in browser
  6. 6. Why Office 365 for this project?•  Different type of users –  Single Sign On with AD sync•  High availability•  No extra IT staffing needed•  Good cost overview•  Secure
  7. 7. Biggest succes factor•  Microsoft takes care of IT –  Updates •  Hotfixes, Service Packs –  Upgrades •  New functionality like BCS –  Scaling •  Extra capacity
  8. 8. The approach•  Agile (7 sprints) –  Product backlog Per sprint –  Stayed as close as possible to OOTB •  Configuration •  Styling –  If required then custom development
  9. 9. The team•  Product owner•  Project manager customer•  Developer –  NL and India•  Designer•  Architect/team lead•  Project manager
  10. 10. Tools•  Visual Studio –  Powerfull tool for developers –  Only sandboxed solutions for Office365 Development takes more time•  SharePoint Designer –  Rapid development –  Reusable workflows required for our project
  11. 11. DTAP environment•  Local development machine•  Test in the cloud•  Acceptance/Production in the cloud Risk for early adoptors (beta products) Sandbox solutions makes deployment easy Office365 environment is quickly available
  12. 12. Deployment•  Same deliverables as ‘normal’ SP project –  Web parts –  Page layouts –  Master pages –  WSP’s –  Documentation
  13. 13. Deployment challenges•  How to deploy the site structure?Normal way of deployment not possible:•  No PowerShell•  No console apps•  No content database copy
  14. 14. Deployment solutionOptions:•  Site templates•  Migration tools –  Different tools available Tool together with Web templates Deployment more difficult
  15. 15. Lessons learned•  Some 3d party tools not usable•  Rapid development with the right tools•  Limitations of Sandbox asks for more creativity•  Use web templates for deployment•  Environment quickly available•  New functionality added to Office365
  16. 16. SummaryWith Office365 you can create powerfullsolutions like on premise. You just needsome more creativity
  17. 17. The development challenges
  18. 18. DevelopmentFirst challenge: Aggregation(How may SiteCollections do I need?)
  19. 19. DEMO: How to extend the CQWP to fit your needs
  20. 20. Aggregation•  OOTB aggregation•  Easy to configure•  Easy to brand
  21. 21. AggregationWhat to do with aggregation over multiple Site Collections?
  22. 22. DEMO: Configure Search to fetch cross- sitecollection data
  23. 23. AggregationAnother cool way of getting data!
  24. 24. DEMO: Configure CQWP + RSS to fetch cross-sitecollection data
  25. 25. Sandboxed SolutionAbout Sandboxed Solutions.. Farm Webapplication Site Collection Site
  26. 26. Sandboxed Solution(#seats × 200) + 300
  27. 27. Sandboxed Solution AbnormalProcessTerminationCount CPUExecutionTime CriticalExceptionCount InvocationCount PercentProcessorTime ProcessCPUCycles ProcessHandleCount ProcessIOBytes ProcessThreadCount ProcessVirtualBytes SharePointDatabaseQueryCount SharePointDatabaseQueryTime UnhandledExceptionCount UnresponsiveProcessCount
  28. 28. Sandboxed Solution•  Deployment•  Limited but Powerful•  Resource Points System•  SiteCollection context only
  29. 29. Client Object ModelFinding the Balance with COM (Client Object Model)
  30. 30. DEMO: Sandboxed WebPart with CSOM
  31. 31. Client Object Model About COM …
  32. 32. Client Object Model No Resource Points Possibilities same as sandboxed•  More code•  Tools less mature then VS
  33. 33. DEMO: All put together, real world SP Online example
  34. 34. SummaryWith Office365 you can create powerfullsolutions like on premise. You just needsome more creativity!
  35. 35. Questions?Resources•  http://msdn.microsoft.com/en-us/library/gg615462.aspx•  http://community.office365.com/en-us/f/145/t/8959.aspx•  @rikdekker•  @casvaniersel•  rik.dekker@rapidcircle.com•  cas.van.iersel@rapidcircle.com Visit our booth!

×