2014 SP Summit Vancouver Bottom Up SharePoint
Download as PPTX, PDF2 likes675 views
Is the landing page the most important part of the Intranet? The answer may surprise you. In this presentation we discuss how Intranet have traditionally been designed and developed and propose a new method that starts with the value at the bottom of the pyramid of SharePoint.
More Related Content
Similar to 2014 SP Summit Vancouver Bottom Up SharePoint (20)
More from David Broussard (16)
Recently uploaded (20)
2014 SP Summit Vancouver Bottom Up SharePoint
- 1. Building Your Intranet From The Bottom Up David C. Broussard– Principal Consultant, Catapult Systems
- 2. www.sharepointsummit.org What is an Intranet? 2
- 3. The four verbs of the Intranet www.sharepointsummit.org Intranet Engage Produce Innovate Decide 3
- 4. How have we always built them? www.sharepointsummit.org 4 Landing Page Division Front Doors Department Collaboration Ad Hoc Collaboration OneDrive for Business Messaging Collaboration G o v e r n a c e
- 5. But…it takes so long www.sharepointsummit.org • Top Intranets take time, people, and money • Average Development takes almost 2 years! • Average Team Size is 18 people • Designers • Authors • Developers • Etc. • Total cost over $1M • Mix of internal and external staff • Cost of servers, licenses, salaries, etc. 80% use SharePoint 5 Nielsen Norman Group – Intranet Design Annual 2013
- 6. www.sharepointsummit.org A highly structured organization is at risk of becoming irrelevant in a quickly changing marketplace… And it’s hard to change
- 7. True or False? www.sharepointsummit.org • The Landing Page is the Most Important Page in the Intranet? 7
- 8. What matters most to the user? www.sharepointsummit.org 8 "Product successes and failures have shown repeatedly that users don't care that much about features. Users only care about achieving their goals." -The Inmates Are Running the Asylum, Alan Cooper
- 9. www.sharepointsummit.org Focus on the Landing Page The traditional approach… 9
- 10. What is the Landing Page? www.sharepointsummit.org 10
- 11. What is the Landing Page? www.sharepointsummit.org Is the purpose of a landing page a place where the user can accomplish something, or a place where they find a link to accomplish something? 11
- 12. The Pyramid of SharePoint Value www.sharepointsummit.org 12 Landing Page Division Front Doors Department Collaboration Ad Hoc Collaboration OneDrive for Business
- 13. The Information Portal as Landing Page www.sharepointsummit.org 13
- 14. www.sharepointsummit.org Case Study HEB Grocers – Information Portal
- 15. HEB – Regional Grocer www.sharepointsummit.org 15 Scenario: • 60,000 users across many locations • Onboarding process is unique for each job level • Security of information is essential. Need: • Personalized portal for each of my users where they can find life event information, benefit forms, online training and access to other applications quickly and easily. • Especially for the Store Leaders because they manage all types of employees.
- 16. HEB Regional Grocer www.sharepointsummit.org 16
- 17. www.sharepointsummit.org How does it get built? Traditional Top Down 17
- 18. MSF Waterfall Approach – In Theory www.sharepointsummit.org Envisioning • Vision/Scope Document • Project Plan and Schedule Planning • BRD • TSD • Governance • Test Plan Developing • Code Assets • Test Scripts Stabilization • Test Results • Training Deploying •Deployment Guide •Project Close- Out
- 19. MSF In Reality www.sharepointsummit.org • Deployment Guide • Project Close- Out 19 Envisioning • Vision/Scope Document • Project Plan and Schedule Planning • BRD • TSD • Governance • Test Plan Developing • Code Assets • Test Scripts Stabilization • Test Results • Training Deploying
- 20. So, what’s the big issue? www.sharepointsummit.org We know that building an Intranet is hard, expensive, and takes a long time…so why don’t we just deal with it? Can’t we just tell management that they need to give us $1M+ and 18+ months and trust us to deliver value at the end? How do we show value faster? 20
- 21. www.sharepointsummit.org A New Approach Build from the Bottom Up 21
- 22. What are our Goals? www.sharepointsummit.org 1. Deliver Business Value Rapidly i. The Business needs to see value from Day 1 ii. Value must map to existing strategic goals iii. Goals will change and thus our Intranet must be adaptive 2. Lay a foundation for future growth i. We cannot design our way into a corner ii. Each portion of the Intranet needs to be “part of the holistic solution” iii. Each portion needs to stand on its own
- 23. Oh, well, that’s simple then… www.sharepointsummit.org 23
- 24. Canadian Pacific Railroad Approach www.sharepointsummit.org
- 25. Top Down and Bottom Up www.sharepointsummit.org 25 Landing Page Division Front Doors Department Collaboration Ad Hoc Collaboration OneDrive for Business
- 26. Turning This… www.sharepointsummit.org • Deployment Guide • Project Close- Out 26 Envisioning • Vision/Scope Document • Project Plan and Schedule Planning • BRD • TSD • Governance • Test Plan Developing • Code Assets • Test Scripts Stabilization • Test Results • Training Deploying
- 27. Into This… www.sharepointsummit.org 27 Envisioning Planning Developing Stabilization Deploying Planning Developing Stabilization Deploying Planning Developing Stabilization Deploying
- 28. Bending the Value Curve www.sharepointsummit.org Day 1 - OneDrive Month 1 – Ad Hoc Sites Month 2 – Department Sites Month N – Continual Improvement 28
- 29. Coming all together… www.sharepointsummit.org 29 Landing page Functional Areas Perm Collab Ad Hoc Collaboration Personal Collaboration
- 30. What does the journey look like? www.sharepointsummit.org 1. Define the Vision 2. Map To Value 3. Work the Solution 4. Evaluate, Adapt, & Iterate 30
- 31. www.sharepointsummit.org Practical Example Oil and Gas Services Company 31
- 32. Oil and Gas Services Company www.sharepointsummit.org 32 Scenario: • 3,000 users across many locations, 700 Information Workers • No “owner” for intranet • Currently on SharePoint 2003 with unstable farm • Own Office 365 E1 Plan for 700 users Need: • Promote culture of Safety throughout company • Provide reports to decision makers throughout the company • Must get off unstable farm • Build momentum with quick wins to gain traction across the company
- 33. Define the Vision www.sharepointsummit.org • Work with the business to identify the strategic drivers for the Intranet • Meet with end users to find out how they work, what their goals and needs are • Create a vision for the project that the client agrees on “We will create an information workplace for our users allowing them to share knowledge and work efficiently” 33
- 34. Map to Value www.sharepointsummit.org • From the user interviews we will build User Stories that define their normal tasks and activities • These stories will be ranked for importance to the company and project • Each User Story will get a work estimate 34
- 35. Work the Solution www.sharepointsummit.org • Identify the Top ranked User stories that fit into the first iteration • Team will work the list items daily • If an obstacle can’t be cleared, put item on hold and move to the next one • Goal is to deliver early and get feedback from the end users • How big or small can a unit of work be? 35
- 36. Evaluate, Adapt, & Iterate www.sharepointsummit.org • As each iteration draws to a close two things must happen 1. Each item worked on must be deployed 2. Next Iteration must be planned • User Stories can be added or removed • Priorities can be changed • Delivered work is monitored for adoption and potential improvements • Overall solution is re-aligned with goals 36
- 38. Pros and Cons www.sharepointsummit.org Pros: • Delivers value faster • Allows for changing priorities Cons: • More difficult to manage process • Easy to lose sight of the “big picture” 38
- 39. Thank you for your attention! This presentation will be available on the Vancouver SharePoint Summit website a few days after the event.
- 40. Please rate this session! Fill out the survey form
Editor's Notes
- #6: Jakob Nielsen Top 2013 Intranets
- #7: This organizational model has worked well to an extent. But it imposes costs. A highly structured organization is oftentimes a rigid, inflexible organization that cannot adapt quickly to a changing marketplace.
- #13: What does the pyramid mean? One interpretation (original) was that it showed the increasing number of instances at each level (1 landing page, a few DFDs, 1 Dept for each dept, many ad hoc collab, 1 MySite/OneDrive for each employee) I used to show this in the reverse (to show the importance of the top and decreasing amount of work as you go down But, this also shows the value proposition…especially when you look at value against development cost
- #14: By combining lots of personalized widgets, we can craft a page that is specific for a particular use…with specific content for them
- #21: Let me know how that works for you…
- #22: Still, the landing page is hard to build, and take a long time. We have to get it just right
- #25: Craigellachie, British Columbia Craig – uh- loxie -- I THINK!!! Between Revelstoke and Sicamous