Build, Customize Or Buy? When Should We Use SharePoint, 3rd Party Products or Build Outside of SharePoint?

1. Richard Harbridge Microsoft (USA) BUILD, CUSTOMISE OR BUY? WHEN SHOULD WE USE SHAREPOINT, 3 RD PARTY PRODUCTS OR BUILD OUTSIDE OF SHAREPOINT

2. My Name Is: Richard Harbridge My Twitter ID: @RHARBRIDGE Microsoft SharePoint Certifications 10 5650 + Personal Connections On LinkedIn Partner Technology Strategist With Microsoft Presented 160+ Sessions Or Workshops In The Past 4 Years

3. Our Goal Today… From Here To Here #Share4Biz @RHarbridge Presented By: Richard Harbridge

4. What Will We Cover Today? Build vs Buy – What’s The Right Answer ? Why Is this So Difficult With SharePoint? How Do We Extend On Top Of SharePoint? How Do We Buy 3 rd Party Products? Review Of Resources #Share4Biz @RHarbridge Presented By: Richard Harbridge

5. Build vs Buy What’s The Right Answer?

6. Image from: http :// partners.varphonex.com/solutions/build-or-buy.php Most Content/Research Will Be Biased

7. Pros & Cons To Build vs Buy Buy Pros Cons Often covers most of the requirements Less flexibility and control Vendor does enhancements/upgrades Dependence on vendor delivery Lower total cost of ownership Locked in on cost and interoperability Build Pros Cons Addresses your requirements best Dependent on internal expertise/effort Full control and flexibility Higher risk of poor documentation Control over costs No economies of scale, higher costs

8. Risks To Build Vs Buy

9. Example Capability Assessment Framework For Build vs Buy

10. The Outcome There are risks in build vs buy that should be understood and re-evaluated constantly .

11. What to watch out for… Each build vs buy decision should be evaluated even when it appears self-evident.

12. Why Is This So Difficult With SharePoint ?

13. Map the needs of the organization to the right technology …

14. This is important as Microsoft alone has a quite a few… Dynamics CRM Dynamics ERP Dynamics AX Dynamics GP Dynamics NAV Dynamics SL Exchange Lync

15. Even SharePoint has multiple options Online On Site Foundation Standard Enterprise Enterprise Standard 2010 2013 Foundation

16. It’s Big Ecosystem… “Worldwide more than 700,000 developers work with SharePoint .” - SPC11 Keynote “ Well over 4,000 partners in the SharePoint ecosystem.” - SPC11 Keynote “There are over 1,000 products since SP2003 – there are at least 1,000 new products in development now. ” - SPC11 Keynote (From Memory)

17. SharePoint is not a Silver Bullet … SharePoint is not a Silver Bullet at NothingButSharePoint.com

18. SharePoint Is Part Of An Overall Enterprise Technology Plan

19. The Outcome We have to understand what technology we have available and our needs .

20. What to watch out for… We have to define our needs carefully if we want to pick the right technology.

21. How Do We Extend/Build On SharePoint?

22. How Do We Build On SharePoint?

23. How Do We Build On SharePoint?

24. The Main Point of Implementing SharePoint: SharePoint eventually allows Business Users to develop and implement business solutions that use technology without IT’s direct involvement. SharePoint and IT Enable Solutions

25. Users Build Apps

26. Users Build Lists To Solve Problems To Replace Excel Spreadsheets To Track Complex Input From Multiple People To Centralize Storage and Retrieval of Content To Provide Validation, Easy To Use Online Forms To Reduce Duplication of Effort

27. How Do We Build On SharePoint?

28. When I Say “SharePoint Integration” You Probably Think Of This... Secondary (But Important) Points: SharePoint’s integration with technologies you already use and it’s extendibility are invaluable. SharePoint and IT Exchange Lync

29. SQL vs SharePoint

30. How Do We Build On SharePoint?

31. The Outcome SharePoint is a platform that makes it easy to extend and leverage for business challenges.

32. What to watch out for… Sometimes it can be easier to start simple with an extended solution to validate/identify needs .

33. How Do We Buy Third Party Products

34. How Do We Buy 3 rd Party Products ?

35. Let’s Discuss Scenarios

36. How Do We Buy 3 rd Party Products ?

37. Buying The Right Migration Tool …

38. Scenario: Migrating To Office 365

39. Buying The Right Migration Tool …

40. Buying The Right Migration Tool …

41. No Practical Option OOTB

42. Buying The Right Migration Tool …

43. Buying The Right Migration Tool …

44. What Type Of Migration Tool Do We Need?

45. Buying The Right Migration Tool …

46. Buying The Right Migration Tool …

47. What Vendor Should We Use? What version is the product?  How mature is the product? How mature is the product’s supporting ecosystem and vendors? How extensible and customizable is the product? How user friendly and usable is the product? How does the product handle exceptions?  For whom is the UI designed? How difficult is it to manage and administer the product? How do you update the product? How complex is the installation and how complex are the dependencies? Does it support automation? (Can you batch script or automate administrative tasks?) Who else is using the tool? What is their experience of the tool like? Do they have similar needs? Product Applicability (Based On Product Proof Of Concepts/Demonstrations) Detailed Price Proposals (Including Estimates for Integration Costs, Support, and Training)

48. Buying The Right Migration Tool …

49. Buying The Right Migration Tool …

50. How Do We Compare The Tools? What Questions Should We Ask? Tough Migration Decisions Whitepaper

51. Buying The Right Migration Tool …

52. Buying The Right Migration Tool …

53. Let’s Discuss Scenarios

54. How Do We Buy 3 rd Party Products ?

55. How Do We Buy 3 rd Party Products ?

56. Buying The Right Permissions Tool …

57. Scenario: Permissions Support

58. Buying The Right Permissions Tool …

59. Buying The Right Permissions Tool …

60. Not Enough Capabilities OOTB

61. Buying The Right Permissions Tool …

62. Buying The Right Permissions Tool …

63. What Permissions Tool Do We Use?

64. Buying The Right Permissions Tool …

65. Buying The Right Permissions Tool …

66. What Vendor Should We Use? What version is the product?  How mature is the product? How mature is the product’s supporting ecosystem and vendors? How extensible and customizable is the product? How user friendly and usable is the product? How does the product handle exceptions?  For whom is the UI designed? How difficult is it to manage and administer the product? How do you update the product? How complex is the installation and how complex are the dependencies? Does it support automation? (Can you batch script or automate administrative tasks?) Who else is using the tool? What is their experience of the tool like? Do they have similar needs? Product Applicability (Based On Product Proof Of Concepts/Demonstrations) Detailed Price Proposals (Including Estimates for Integration Costs, Support, and Training)

67. Buying The Right Permissions Tool …

68. Buying The Right Permissions Tool …

69. How Do We Compare The Tools? What Questions Should We Ask? While a resource like the migration one doesn’t always exist for this ( and many other purchase decisions ) you should always ask questions that validate/clarify needs.

70. Buying The Right Permissions Tool …

71. Buying The Right Permissions Tool …

72. Additional Scenarios

73. Social SharePoint Options When are people going beyond SharePoint for Social Functionality? How To Lock Down SharePoint’s Social Features

74. Additional Scenarios

75. SharePoint Workflow Options

76. The Outcome With clear needs and the right questions you can select the right tool.

77. What to watch out for… The hardest part of selecting the right third party tool is having the right questions .

78. Review Of Resources

79. SharePoint Reviews.com

80. Office Store (Apps for SharePoint)

81. Analysts, Customers & Consultants

82. Vendor Whitepapers/Content Many vendors are not always biased, and often even when biased highlight important decision criteria/questions.

83. Migration Decisions Whitepaper http://info.portalsolutions.net/MigrationWhitepaper_WhitepaperDownload.html