SharePoint Best Practices Conference 2013


Published on

Presentation given by David R. Knight, Intel Corp., at the 2013 SharePoint Best Practices Conference hosted by Mindsharp, a subsidiary of EBA. Inc.,

Published in: Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Speaker Notes:Today Intel’s Embedded Communications Group supports over 30 different market segments, literally serving 1,000s of customers in applications like the ones you just saw.Here is a quick snapshot of the 30 markets segments we are playing in today with IA.Intel isn’t a new player in Embedded. We’ve actually been in this business for over 30 years.You can see this is a wide range of market segments that will only continue to grow for IA as we develop new products and solutions to go deeper in these market segments.
  • Using infopath allows the form developer to automatically populate fields, and only show those fields that a user needs to fill out based on other selections. In this case, fields are only shown as a user selects which types of travel they will be using.
  • Don’t ask users to populate the user names for the approvers…do it programmatically.
  • SharePoint Best Practices Conference 2013

    1. 1. 1
    2. 2. 2
    3. 3. 3Stock InfoNASDAQ: INTCDow Jones Industrial Average ComponentNASDAQ-100 ComponentS&P 500 ComponentIndustry SemiconductorsFounded July 18, 1968Founder(s) Gordon Moore, Robert NoyceHeadquarters Santa Clara, California, United StatesProductsMicroprocessors, SOCs, SSDs, Software, Bluetoothchipsets, flash memory, motherboard chipsets, network interfacecards…Revenue US$ 53.34 billion (2012)OperatingincomeUS$ 14.63 billion (2012)Net income US$ 11.00 billion (2012)Total assets US$ 84.35 billion (2012)Total equity US$ 51.20 billion (2012)Employees 104,700 (2012)Website Intel.comIntel Corporation
    4. 4. 4• 2,095 Full-time Employees, Interns, and Contingent Workers• Birthplace of Intel Atom Processor & Atom SoCs (2007)• Ultra-low-power & low-cost devices for smartphones,tablets, netbooks, & embedded applications.• Cost between $19 and $64• Power consumption between 1.4 and 8.1 Watts• Allows tablets as thin as 8.5 mm and 1.5 lbs in weight• Provides up to 10 hours of local HD video playbackIntel AustinClover Trail(Targeting tablets/convertibles)Penwell, Medfield platform(Targeting SmartPhones)
    5. 5. 5DigitalSignageRoboticsDigital SecuritySurveillancePrintersTransportationTest &MeasurementNetworkAppliancesWirelessInfrastructureRouting &SwitchingEnterpriseVoIPEnterpriseSecurityIP ServicesMilitary ATM MedicalImagingGamingAerospace KiosksPoint of SaleIndustrial PC Thin ClientIn-VehicleInfotainmentMedicalPortableIP CamerasHomeAutomationSensors ResidentialGatewayIP MediaPhonesFactoryAutomationEnergy& UtilitiesControlAtom is Everywhere:More than 30 Segments and 1,000’s of CUSTOMERS
    6. 6. 6Speaker IntroDavid R. Knightdavid.r.knight@intel.comHome Site: Austin, TexasEmployed at Intel Corporation for 16 years• Austin Site IP & Asset Protection Manager (1 year)• Operational Tools & Technologies Manager (5 years)– Microsoft SharePoint Server 2010– Microsoft Office SharePoint Server 2007• Knowledge Manager, Information Architect (4 years)– Microsoft SharePoint 2003– Microsoft SharePoint Portal Server 2001• Sr. Application Performance & Tuning Engineer (3 years)– Microsoft SharePoint Portal Server 2001• Sr. Software Engineer in Server Firmware Division (3 years)
    7. 7. 7My SharePoint Environment• Intel has 3 isolated geographic SharePoint farms• Intel‟s business groups are separate P&L orgs• I am not in the Information Technology (IT) team• Try to influence IT, but they are much bigger than me• I do not have access to central admin• Tens of thousands of discrete, isolated site collections
    8. 8. 8Image Source:
    9. 9. 9Primary Use of Microsoft SharePointTo Eliminate: Eliminate overhead, pointless approvalloops, no-value added steps, manualstatus changes, manual update to routingduring approvers vacation, etc.To Automate: Automate business process, approvalflows, award submissions, travel &housing requests, cateringrequests, performance indicators, etc.To Liberate: Liberate our employees frombureaucracy, overhead, and minutia. Freeemployee minds to focus on deliveringamazing products & services.
    10. 10. 10Some Best Practices…1. Eliminate Waste, Automate Processes, andLiberate People and „in‟ boxes with InfoPath,Workflows, and a “LEAN” Mindset2. Separate Project Sites from Organizational Sites3. Remove Access Entitlement From SharePoint4. Separate Environments for Standard andExtreme Power Users5. Turn on Useful Features6. Enable ERMDetour: What didn‟t work7. Follow the Traffic
    11. 11. 11Best Practice #1 : Eliminate, Automate & Liberatewith InfoPath, Workflows, and a “Lean” Mindset
    12. 12. 12Best Practice #1 : Eliminate, Automate & Liberatewith InfoPath, Workflows, and a “Lean” Mindset
    13. 13. 13Best Practice #2 : Separate Project Sitesfrom Organizational Sites• Organizational Sites Contain Generalized Info• Org Charts• Missions• Strategic Objectives• Operational Updates• Awards• Project Sites have Info Critical to Develop a Product/Service• Architecture Diagrams• Test Plans• Benchmarks• Project Indicators• Project plans• Test programs• Diagrams• CodeOPEN ACCESSRESTRICTED ACCESSMost members work forsame managementteamMost members work indifferent groups,divisions, and teams
    14. 14. 14Best Practice #2 : Separate Project Sitesfrom Organizational SitesOrganizational Site, Customized,Branded, etc.Project Site Out-of-Box
    15. 15. 15Best Practice #3 : Remove AccessEntitlement From SharePointPermissions Tool:• Ensures Training Compliance• Checks for Control Country• Sets Expirations• Creates Audit Trail• Moves approval to contentowners vs. site/doclib owners
    16. 16. 16Best Practice #4 : Separate Environmentsfor Standard and Extreme Power Users• Standard environment for 80% of employees• No access to modify master or layout pages• Active scripting in CEWP or WIKI pages blocked• No Visual Studio Workflows allowed• Minimal availability to change look/feel or branding of site• Allows for IT to do “Sunrise Migrations” to future versions• SCOs will never have to migrate their own content to future versions• 20% of employees are super users or require sites with high customization inbranding.• Master and Layout pages can be edited on the local site collection• Visual Studio used sparingly• Active scripting allowed• SCOs must migrate their content, code, and recreate branding efforts on futureversions of SharePoint• Tradeoff of providing high flexibly to SCOs vs easy migration
    17. 17. 17Best Practice #5 : Turn on Useful Features
    18. 18. 18Best Practice #6 : Enable ERM…
    19. 19. 19Detour: What Didn’t Work…Using SharePoint as the only toolfor EVERYTHING• Collaboration• File Share• WIKI• Discussion Board• Surveys• Expert Finder• Development Opportunity Tool• Mentorship Tool• Media Library• Etc…
    20. 20. 20Practice #7: Follow the Traffic• Although SharePoint has wikis and discussions boardsand lots of other stuff, you may not want to use them.• We have massive adoption to SecureWIKI (Internal name for 3rd PartySoftware) and PlanetBlue (Internal Name for 3rd Party Software)• Link from SharePoint to SecureWIKI or PlanetBlue,rather than try to pull people to your SharePoint‟sWIKIs and Discussions Boards• People from a project website click on discussion linkand leave SharePoint• WIKIs have links to files that are stored on SharePoint*Trademarks, names and/or brands are the property of the cited companies
    21. 21. 21
    22. 22. 22