Your SlideShare is downloading. ×
0
The Seven Most Important Non Technical SharePoint Success Factors<br />Presented By: Richard Harbridge<br />@rharbridge<br />
Who am I?<br />I<br />
Understanding the Non Technical<br />The Biggest ReasonsSharePoint Projects Fail?<br />Is necessary to avoid poor…<br /><u...
Knowledge around Limitations of the Software 	(When to use it/When not to)
Estimation of Effort and Schedule Accuracy</li></li></ul><li> Our Goal Today…<br />From Here                              ...
What we will be talking about…<br />Understanding the ‘Why’ & Making a Decision<br />Achieving Buy In and Setting Expectat...
Understanding the ‘Why’ and Making a Decision<br />
Meet Joe<br />Hi!<br />
At Joe’s Company…<br />
Decision Makers don’t have Enough Information<br />
The CFO needs to Reduce Costs<br />
IT Services Struggles to Keep Up<br />
And<br />People Are Having Trouble Finding What They Need<br />
So Joe has an Idea!<br />
Since…<br />Awesome!   <br />Not as awesome.<br />
And Everyone in Joe’s Company uses Microsoft Office…<br />
SharePoint is the Perfect Fit!<br />
Map the needs of the organization to the right technology…<br />
Perform in depth product comparisons and evaluations<br />
Like this <br />one…<br />Excerpt of Product Comparison written by Richard Harbridge courtesy of Concept Interactive<br />
This is important as Microsoft alone has a quite a few…<br /><ul><li>Dynamics AX
Dynamics CRM
Dynamics GP
Dynamics NAV
Dynamics POS
Dynamics RMS
Dynamics SL</li></li></ul><li>2007<br />Online<br />On Site<br />Even SharePoint has multiple options<br />2010<br />
It’s not just a feature to feature comparison<br />
So Joe does all that good research and…<br />
SharePoint is a part of his overall Enterprise Technology Plan<br />
The Outcome<br />Within the overall enterprise technology plan SharePoint meets specific business needs.<br />
What to watch out for…<br />We have to define our needs carefully if we want to pick the right technology.<br />
Achieving Buy In and Setting Expectations<br />
Before we begin…<br />
Let’s Talk About Perceptions<br />
People See Different Things<br />
Perceptions Impact Motivation<br />
Two Key Groups Must Buy In and Have The Right Expectations<br />IT Services<br />Decision Makers<br />
What is the most important thing to IT Services?<br />
COST OF OWNERSHIP<br />
What are some ways we can convince IT Services?<br />
Cost of Ownership (IT)<br />The Biggest Point to Share is:<br /><ul><li>SharePoint eventually allows Business Users to dev...
SharePoint’s integration is invaluable to IT.
A unified application delivery platform like SharePoint can greatly reduce costs, time and effort for new work.</li></li><...
Explain Platform Benefits<br />
What is the most important thing to Decision Makers?<br />
Add Value To Business<br />
What are some ways we can convince Decision Makers?<br />
Add Value (Decision Makers)<br />The Biggest Point to Share is:<br /><ul><li>SharePoint can help achievebusiness objective...
It takes time and investment to reach the point all managers and executives want. </li></li></ul><li>Prioritize and Plan<b...
Map Solutions to Objectives<br /> Direct Relationship	Indirect Relationship<br />* Objectives should be more specific – ...
What’s the expectationwe have to set?<br />
It Takes Time<br />
SharePoint Solutions (Evolution)<br />*Super Simplified<br />
The Outcome<br />Joe has achieved momentum and buy in.<br />
What to watch out for…<br />Joe must carefully manage expectations and maintain the momentum.<br />
Determining and Supporting ROI<br />
How do we get here?<br />
Evaluating With Discounted Cash Flow<br /><ul><li>Show expected cost and return over multiple time periods.
Remember to ‘discount’ values to account for cost of capital impact and the fact $5 dollars today is worth less than $5 in...
Evaluating with Monte Carlo Analysis<br />
There are different ways of calculating ROI<br />This is kind of boring…<br />
There are really only two <br />ways of using ROI<br />1. For Prioritization<br />2. To Improve Return<br />
1. For Prioritization<br />The Simplest ROI Formula Ever<br />Estimated Value<br />Even I can do it!<br />Estimated Diffic...
1. For Prioritization<br />Examples<br /><ul><li>I have a difficult requirement. It’s an 8 in difficulty (out of 10).
I have an easy requirement. It’s a 2 in difficulty (out of 10).
The expected value of the difficult requirement is 4 (out of 10).
The expected value of the easy requirement is 6 (out of 10).</li></ul>Estimated Value<br />Estimated Difficulty<br />
2. To Improve Return<br />ROI (traditionally) Measures Financial Impact<br />
2. To Improve Return<br />ROI analysis often  misses 'non-financial impact’ or ‘increased potential’<br />STILL <br />IMPO...
2. To Improve Return<br />Example of Non-Financial Measurement<br />
IS <br />Use them.<br />
SharePoint Deployment Planning Services (SDPS)<br />https://www.partnersdps.com/Pages/ToolsSupport.aspx<br />
Rapid Economic Justification Guide<br />http://www.microsoft.com/business/enterprise/value.mspx<br />
MEASURE THE RIGHT THING<br />
What you don’t want.<br />Don’t lose perspective.<br />
The Outcome<br />Joe is measuring effort effectively to better prioritize or to improve return on investment.<br />
What to watch out for…<br />Fear of bad estimation leading to not estimating at all. Vaguely right is better than precisel...
Implementing Successful Governance<br />
What is Governance?<br />
GOVERNANCE IS REQUIRED<br />
What does that mean?<br />Without effective governanceorganization, performance, andcapability are significantly reduced.<...
Without Governance<br />
So how do we do it?<br />
Teamwork is Key<br />There are typically 5 teams for SharePoint Governance:<br /><ul><li>Business Strategy Team
Initiatives/Technical Strategy Team
Tactical Teams:
Tactical Operations Team
Tactical Development Team
Tactical Support Team</li></li></ul><li>Alternative Teams<br />If the organization or implementation is small enough you m...
Operations
Development
Support
Strategy Team
Business
Technical</li></li></ul><li>Identify patterns.Plan for patterns.Execute patterns.<br />
I think I see a Pattern.<br />
Executing Governance<br />
No Single “Approach”<br />Projects<br />Communities<br />Tasks<br />Practices<br />
Governance Deliverables<br /><ul><li>Aggregate/Reference Document or Site(Contains all SharePoint Info – Single Point of R...
Objectives/Priorities (Tech/Business)</li></li></ul><li>SharePoint will be…<br /><ul><li>Utilized by Business Users to dev...
Our primary unified application delivery platform.
Our primary workflow/business process automation platform.
Our intranet and communication center for internal corporate communications.
…</li></ul>SharePoint will not be…<br /><ul><li>Our (external) web content management platform.
Our primary document management platform.
Our contact management platform.
…</li></li></ul><li>Operations Deliverables<br /><ul><li>Objectives/Priorities
Disaster Recovery Plan
Storage and Quota Policies
Monitoring Plans
Maintenance Plans
Service Level Agreements
Security Policies
Deployment Process, Policies, and Schedule</li></li></ul><li>Development Deliverables<br /><ul><li>Objectives/Priorities
Branding Guide
SharePoint Designer Policy
Workflow Policy
Development Standards (Including OOTB vs Custom)
Development Environment Policy
Testing Requirements
Deployment Process, Policies, and Schedule</li></ul>SharePoint Standards Online<br />
Support Deliverables<br /><ul><li>Objectives/Priorities
Site Classification and Platform Classification
Site Provisioning Process/Questionnaire
User Expectations Agreement
Roles and Responsibilities
Support Agreement(s)
Training and Communication Plans
MySite Policies (Pictures)…</li></li></ul><li>IS <br />Use them.<br />
Governance Checklist<br />
TechNet, Community and More..<br />
With Governance<br />
The Outcome<br />Everyone Achieves a Shared Understanding of SharePoint Related Processes<br />
What to watch out for…<br />Not just documents, policies, and procedures. It is an active and ongoing process.<br />
Approaching and Supporting SharePoint<br />
What is the best approach for SharePoint Implementations?<br />
ITERATIVE APPROACH<br />
Upcoming SlideShare
Loading in...5
×

SharePoint Saturday Redmond - The Seven Most Important (Non Technical) SharePoint Success Factors

692

Published on

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

No Downloads
Views
Total Views
692
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
29
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • My dedication to you before I begin. By the end of this you will have gained 3 things. It might be new knowledge, it might be a new method but you MUST gain 3 things by the end. If you don’t my first challenge to you is to stalk me, hunt me down and make sure you get 3 things from me. Because I owe you 3 things! This is meant to help you. 
  • You take the estimated value and divide that by the estimated level of difficulty then times (*) it by 100 to get the percentage of ROI.
  • You take the estimated value and divide that by the estimated level of difficulty then times (*) it by 100 to get the percentage of ROI.
  • Ask every question three times in three different ways - Might get it wrong, might be mis-estimating their technical vocabulary/abilityUse Pictures - Pictures and moreeee pictures.
  • Dependency also works.
  • A lot of this can seem daunting and I know one of the hardest things is figuring out how to do some of the things I have shown today. If you are interested in further training or assistance please let me know. Based on the number of people who are interested and the areas of interest we can schedule further training sessions to help everyone better use the SharePoint portal.It&apos;s our commitment to you that we will continue to hear your feedback and identify the issues. I encourage you to give us feedback during the coming months, and we will continue to deliver more and more functionality, more and more guidance to help you be successful with your application of SharePoint.Thank You for Reading/Listening
  • A lot of this can seem daunting and I know one of the hardest things is figuring out how to do some of the things I have shown today. If you are interested in further training or assistance please let me know. Based on the number of people who are interested and the areas of interest we can schedule further training sessions to help everyone better use the SharePoint portal.It&apos;s our commitment to you that we will continue to hear your feedback and identify the issues. I encourage you to give us feedback during the coming months, and we will continue to deliver more and more functionality, more and more guidance to help you be successful with your application of SharePoint.Thank You for Reading/Listening
  • Transcript of "SharePoint Saturday Redmond - The Seven Most Important (Non Technical) SharePoint Success Factors"

    1. 1. The Seven Most Important Non Technical SharePoint Success Factors<br />Presented By: Richard Harbridge<br />@rharbridge<br />
    2. 2. Who am I?<br />I<br />
    3. 3. Understanding the Non Technical<br />The Biggest ReasonsSharePoint Projects Fail?<br />Is necessary to avoid poor…<br /><ul><li>Shared Understanding of Requirements/Needs
    4. 4. Knowledge around Limitations of the Software (When to use it/When not to)
    5. 5. Estimation of Effort and Schedule Accuracy</li></li></ul><li> Our Goal Today…<br />From Here To Here<br />
    6. 6. What we will be talking about…<br />Understanding the ‘Why’ & Making a Decision<br />Achieving Buy In and Setting Expectations<br />Determining and Supporting ROI<br />Implementing Successful Governance<br />Approaching and Supporting SharePoint<br />Improving User Adoption<br />Planning for New Work and Growth<br />
    7. 7. Understanding the ‘Why’ and Making a Decision<br />
    8. 8. Meet Joe<br />Hi!<br />
    9. 9. At Joe’s Company…<br />
    10. 10. Decision Makers don’t have Enough Information<br />
    11. 11. The CFO needs to Reduce Costs<br />
    12. 12. IT Services Struggles to Keep Up<br />
    13. 13. And<br />People Are Having Trouble Finding What They Need<br />
    14. 14. So Joe has an Idea!<br />
    15. 15. Since…<br />Awesome! <br />Not as awesome.<br />
    16. 16. And Everyone in Joe’s Company uses Microsoft Office…<br />
    17. 17. SharePoint is the Perfect Fit!<br />
    18. 18.
    19. 19. Map the needs of the organization to the right technology…<br />
    20. 20. Perform in depth product comparisons and evaluations<br />
    21. 21. Like this <br />one…<br />Excerpt of Product Comparison written by Richard Harbridge courtesy of Concept Interactive<br />
    22. 22. This is important as Microsoft alone has a quite a few…<br /><ul><li>Dynamics AX
    23. 23. Dynamics CRM
    24. 24. Dynamics GP
    25. 25. Dynamics NAV
    26. 26. Dynamics POS
    27. 27. Dynamics RMS
    28. 28. Dynamics SL</li></li></ul><li>2007<br />Online<br />On Site<br />Even SharePoint has multiple options<br />2010<br />
    29. 29. It’s not just a feature to feature comparison<br />
    30. 30. So Joe does all that good research and…<br />
    31. 31. SharePoint is a part of his overall Enterprise Technology Plan<br />
    32. 32. The Outcome<br />Within the overall enterprise technology plan SharePoint meets specific business needs.<br />
    33. 33. What to watch out for…<br />We have to define our needs carefully if we want to pick the right technology.<br />
    34. 34. Achieving Buy In and Setting Expectations<br />
    35. 35. Before we begin…<br />
    36. 36. Let’s Talk About Perceptions<br />
    37. 37.
    38. 38. People See Different Things<br />
    39. 39. Perceptions Impact Motivation<br />
    40. 40. Two Key Groups Must Buy In and Have The Right Expectations<br />IT Services<br />Decision Makers<br />
    41. 41. What is the most important thing to IT Services?<br />
    42. 42. COST OF OWNERSHIP<br />
    43. 43. What are some ways we can convince IT Services?<br />
    44. 44. Cost of Ownership (IT)<br />The Biggest Point to Share is:<br /><ul><li>SharePoint eventually allows Business Users to develop and implement business solutions that use technology without IT’s involvement.</li></ul>The Reality:<br /><ul><li>IT doesn’t want to learn/support a new technology.
    45. 45. SharePoint’s integration is invaluable to IT.
    46. 46. A unified application delivery platform like SharePoint can greatly reduce costs, time and effort for new work.</li></li></ul><li>Explain Information Overload<br />Information<br />Information<br />Information<br />Information<br />
    47. 47. Explain Platform Benefits<br />
    48. 48. What is the most important thing to Decision Makers?<br />
    49. 49. Add Value To Business<br />
    50. 50. What are some ways we can convince Decision Makers?<br />
    51. 51. Add Value (Decision Makers)<br />The Biggest Point to Share is:<br /><ul><li>SharePoint can help achievebusiness objectives by improving productivity, reducing waste, and improving visibility to help drive better decision making.</li></ul>The Reality:<br /><ul><li>Business Objectives are often not specific enough to be achievable.
    52. 52. It takes time and investment to reach the point all managers and executives want. </li></li></ul><li>Prioritize and Plan<br />
    53. 53. Map Solutions to Objectives<br /> Direct Relationship Indirect Relationship<br />* Objectives should be more specific – Example purposes only.<br />
    54. 54. What’s the expectationwe have to set?<br />
    55. 55. It Takes Time<br />
    56. 56. SharePoint Solutions (Evolution)<br />*Super Simplified<br />
    57. 57. The Outcome<br />Joe has achieved momentum and buy in.<br />
    58. 58. What to watch out for…<br />Joe must carefully manage expectations and maintain the momentum.<br />
    59. 59. Determining and Supporting ROI<br />
    60. 60. How do we get here?<br />
    61. 61. Evaluating With Discounted Cash Flow<br /><ul><li>Show expected cost and return over multiple time periods.
    62. 62. Remember to ‘discount’ values to account for cost of capital impact and the fact $5 dollars today is worth less than $5 in the future.</li></li></ul><li>Evaluating with Real Options Analysis<br />
    63. 63. Evaluating with Monte Carlo Analysis<br />
    64. 64. There are different ways of calculating ROI<br />This is kind of boring…<br />
    65. 65. There are really only two <br />ways of using ROI<br />1. For Prioritization<br />2. To Improve Return<br />
    66. 66. 1. For Prioritization<br />The Simplest ROI Formula Ever<br />Estimated Value<br />Even I can do it!<br />Estimated Difficulty<br />
    67. 67. 1. For Prioritization<br />Examples<br /><ul><li>I have a difficult requirement. It’s an 8 in difficulty (out of 10).
    68. 68. I have an easy requirement. It’s a 2 in difficulty (out of 10).
    69. 69. The expected value of the difficult requirement is 4 (out of 10).
    70. 70. The expected value of the easy requirement is 6 (out of 10).</li></ul>Estimated Value<br />Estimated Difficulty<br />
    71. 71. 2. To Improve Return<br />ROI (traditionally) Measures Financial Impact<br />
    72. 72. 2. To Improve Return<br />ROI analysis often misses 'non-financial impact’ or ‘increased potential’<br />STILL <br />IMPORTANT<br />Improved Relationships<br />Improved Know-How<br />Website/Intranet Visitors<br />Improved Morale<br />Improved Skills<br />User Complaints<br />Increased Connections<br />Positive Word of Mouth<br />Innovation<br />Click-throughs<br />Employment Applications<br />Comments<br />Negative Word of Mouth<br />Better Reputation<br />
    73. 73. 2. To Improve Return<br />Example of Non-Financial Measurement<br />
    74. 74. IS <br />Use them.<br />
    75. 75. SharePoint Deployment Planning Services (SDPS)<br />https://www.partnersdps.com/Pages/ToolsSupport.aspx<br />
    76. 76. Rapid Economic Justification Guide<br />http://www.microsoft.com/business/enterprise/value.mspx<br />
    77. 77. MEASURE THE RIGHT THING<br />
    78. 78.
    79. 79. What you don’t want.<br />Don’t lose perspective.<br />
    80. 80. The Outcome<br />Joe is measuring effort effectively to better prioritize or to improve return on investment.<br />
    81. 81. What to watch out for…<br />Fear of bad estimation leading to not estimating at all. Vaguely right is better than precisely wrong.<br />
    82. 82. Implementing Successful Governance<br />
    83. 83. What is Governance?<br />
    84. 84. GOVERNANCE IS REQUIRED<br />
    85. 85. What does that mean?<br />Without effective governanceorganization, performance, andcapability are significantly reduced.<br />
    86. 86. Without Governance<br />
    87. 87. So how do we do it?<br />
    88. 88. Teamwork is Key<br />There are typically 5 teams for SharePoint Governance:<br /><ul><li>Business Strategy Team
    89. 89. Initiatives/Technical Strategy Team
    90. 90. Tactical Teams:
    91. 91. Tactical Operations Team
    92. 92. Tactical Development Team
    93. 93. Tactical Support Team</li></li></ul><li>Alternative Teams<br />If the organization or implementation is small enough you might only need to start with two and break them apart as you mature/grow.<br /><ul><li>Tactical Team
    94. 94. Operations
    95. 95. Development
    96. 96. Support
    97. 97. Strategy Team
    98. 98. Business
    99. 99. Technical</li></li></ul><li>Identify patterns.Plan for patterns.Execute patterns.<br />
    100. 100. I think I see a Pattern.<br />
    101. 101. Executing Governance<br />
    102. 102. No Single “Approach”<br />Projects<br />Communities<br />Tasks<br />Practices<br />
    103. 103. Governance Deliverables<br /><ul><li>Aggregate/Reference Document or Site(Contains all SharePoint Info – Single Point of Reference)
    104. 104. Objectives/Priorities (Tech/Business)</li></li></ul><li>SharePoint will be…<br /><ul><li>Utilized by Business Users to develop and implement business solutions that use technology without IT’s direct involvement.
    105. 105. Our primary unified application delivery platform.
    106. 106. Our primary workflow/business process automation platform.
    107. 107. Our intranet and communication center for internal corporate communications.
    108. 108. …</li></ul>SharePoint will not be…<br /><ul><li>Our (external) web content management platform.
    109. 109. Our primary document management platform.
    110. 110. Our contact management platform.
    111. 111. …</li></li></ul><li>Operations Deliverables<br /><ul><li>Objectives/Priorities
    112. 112. Disaster Recovery Plan
    113. 113. Storage and Quota Policies
    114. 114. Monitoring Plans
    115. 115. Maintenance Plans
    116. 116. Service Level Agreements
    117. 117. Security Policies
    118. 118. Deployment Process, Policies, and Schedule</li></li></ul><li>Development Deliverables<br /><ul><li>Objectives/Priorities
    119. 119. Branding Guide
    120. 120. SharePoint Designer Policy
    121. 121. Workflow Policy
    122. 122. Development Standards (Including OOTB vs Custom)
    123. 123. Development Environment Policy
    124. 124. Testing Requirements
    125. 125. Deployment Process, Policies, and Schedule</li></ul>SharePoint Standards Online<br />
    126. 126. Support Deliverables<br /><ul><li>Objectives/Priorities
    127. 127. Site Classification and Platform Classification
    128. 128. Site Provisioning Process/Questionnaire
    129. 129. User Expectations Agreement
    130. 130. Roles and Responsibilities
    131. 131. Support Agreement(s)
    132. 132. Training and Communication Plans
    133. 133. MySite Policies (Pictures)…</li></li></ul><li>IS <br />Use them.<br />
    134. 134. Governance Checklist<br />
    135. 135. TechNet, Community and More..<br />
    136. 136. With Governance<br />
    137. 137. The Outcome<br />Everyone Achieves a Shared Understanding of SharePoint Related Processes<br />
    138. 138. What to watch out for…<br />Not just documents, policies, and procedures. It is an active and ongoing process.<br />
    139. 139. Approaching and Supporting SharePoint<br />
    140. 140. What is the best approach for SharePoint Implementations?<br />
    141. 141. ITERATIVE APPROACH<br />
    142. 142. Why Iterative?<br /><ul><li>SharePoint is a very large platform.
    143. 143. It takes time to understand SharePoint.
    144. 144. SharePoint is great for rapid prototyping, and for proof of concept work.
    145. 145. It ensures there is enough time to review, adjust, and communicate.</li></li></ul><li>CommunicationPlanning<br />
    146. 146. TheCommunicationPlan<br /><ul><li>Will act as a binding agreement (forces you to carry through).
    147. 147. Helps keep communication focused.
    148. 148. Helps prevent unwanted surprises.</li></li></ul><li>SupportPlanning<br />
    149. 149. Don’t forget you aren’t superman.<br />(Sorry Joe)<br />
    150. 150. Multiple Tiers for Escalation<br />(You can’t know everything)<br />
    151. 151. Measure Support<br />Learn and use data to be proactive.<br />
    152. 152. Diversify Support<br />resources/mediums<br /><ul><li>Books and Manuals
    153. 153. Online
    154. 154. MSDN
    155. 155. TechNet
    156. 156. Blogs
    157. 157. Cheat Sheets
    158. 158. One on One
    159. 159. Classroom Training
    160. 160. Forums
    161. 161. Help
    162. 162. Etc</li></li></ul><li>Useful, digestible trainingsessions (less than an hour)<br />Workshops > Presentations<br />
    163. 163. Avoid too much too fast.Keep it simple.<br />It’s like learning to drive.<br />
    164. 164. IS <br />Use them.<br />
    165. 165. Productivity Hub<br />
    166. 166. Support Tip…<br />
    167. 167. RESPOND<br />You never want to give the IT busy signal, or support busy signal.<br />
    168. 168. The Outcome<br />SharePoint is supported effectively.<br />
    169. 169. What to watch out for…<br />The training and support can be costly in time and resources.<br />
    170. 170. Improved User Adoption<br />
    171. 171. How do we get successful User Adoption?<br />
    172. 172. USERS MUST UNDERSTAND THE VALUE<br />
    173. 173. Successful User Adoption Requires…<br />
    174. 174. Do a video like this one…<br />
    175. 175. High Availability, Mobility and Accessibility also lead to better User Adoption!<br />SharePoint Workspace/Groove, Outlook Integration (Offlining), Mobile and More <br />
    176. 176. Cultivate and promote the <br />right culture.<br />
    177. 177. Create an Identity and Brand<br />Consistency Across User Environments<br />Modify Provisioned Site (or Templates) Based on Need<br />Branding should make it easier, and more effective.<br />
    178. 178. Focus on those on board/ready.<br />People who already want it.<br />
    179. 179. Make it Fun!<br />Hold Contests, Scavenger Hunts and Other Activities<br />
    180. 180. Use what they love.<br />If they love using outlook focus on using that as a leveraging point.<br />
    181. 181. Say “Thank You”<br />It’s okay to be proud.<br />
    182. 182. Reward super users with achievements. <br />Then promote the desire to get rewards.<br />
    183. 183. Create a SharePoint Showcase<br />Good Idea!<br />Where users submit and show off <br />their SharePoint “Solutions”<br />
    184. 184.
    185. 185. Make it easier to work with<br />
    186. 186. The Outcome<br />SharePoint is successfully adopted by a large enough group of users to be deemed successful.<br />
    187. 187. What to watch out for…<br />The build it they will come approach will not work alone.<br />
    188. 188. Planning for New Work and Growth<br />
    189. 189. What about New Work & Growth?<br />
    190. 190. Spend time in advance building a channel for new work.<br />Avoid the flood.<br />
    191. 191. Know your limits<br />
    192. 192. Growyour team<br />
    193. 193. Knowyour team and needs<br /><ul><li>Developers(s)
    194. 194. Administrators(s)
    195. 195. Architect(s)
    196. 196. Business Analyst(s)
    197. 197. Project Manager(s)
    198. 198. Site Administrator(s)
    199. 199. Super Users(s)
    200. 200. Trainer(s)</li></li></ul><li>Cultivatenew work! It’s a good thing. <br />This boosts user adoption! (More functionality and dependency over time)<br />
    201. 201. The Outcome<br />The SharePoint Implementation continues to grow, expand and provide more value.<br />
    202. 202. What to watch out for…<br />You need to plan support for new work/requests otherwise people will lose confidence.<br />
    203. 203. So being successful requires…<br />Understanding the non technical as well as the technical.<br />
    204. 204. Success Factors…<br />Understanding the ‘Why’ & Making a Decision<br />Achieving Buy In and Setting Expectations<br />Determining and Supporting ROI<br />Implementing Successful Governance<br />Approaching and Supporting SharePoint<br />Improving User Adoption<br />Planning for New Work and Growth<br />Understand Business Needs and Map to Them<br />Share Alignment, Vision and Expectations<br />Use Measurements to Improve and Return More<br />Use Team Work And Execute With Patterns<br />Be Iterative, Leverage Everyone, and Respond<br />Share the Value and Successes<br />Manage your Capability and Priorities<br />
    205. 205. Please Fill Out The Survey<br />Interested in hearing more on these topics? Related sessions are:<br /><ul><li>Effective Requirements Gathering WorkshopsRuvenGotz
    206. 206. Congratulations, You’re THE SharePoint Person In Charge David Griffiths
    207. 207. Information Management: Ontology and Taxonomy Creation</li></ul> Brian Seitz<br /><ul><li>How to Facilitate the Government out of Governance</li></ul> Virgil Carrol<br /><ul><li>SharePoint as a Platform for Business Applications</li></ul> Owen Allen<br />
    208. 208. Thank You Organizers, Sponsors andYoufor Making this Possible.<br />Questions? Ideas? Feedback? Contact me:<br /><ul><li>Twitter: @rharbridge
    209. 209. Blog: www.rharbridge.com
    210. 210. LinkedIn: www.linkedin.com/in/rharbridge
    211. 211. Email me at: richard@rharbridge.com
    212. 212. My company: www.Allin.com</li>
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×