2. Analysis ASP.NET bpr Business Development business process re-engineering C# changemanagementCivilCommunicationsCommunity BuildingContinuity of Operations Cyber Cryptography IT Data Analysis DefenseDHS Diversity Economic & Business Analysis Editing Energy EnterpriseArchitecture event management Enterprise2.0Facilitation Financial Management HealthHomelandSecurity & Law EnforcementGreen Gov2.0Homeland Security Strategy & Operations HTMLInformationAssuranceInfrastructureManagementIT Strategy Java JavaScriptKnowledge ManagementMarketing mentoring mobile Modeling, Simulation, Wargaming & Analysis.NET Oracle Organization and StrategyPerformance Management Partnership PMPManagement projectmanagementProfessional Policy ProcessImprovementProgram Services requirements analysis Remote Delivery Requirement Analysis RFID RiskManagementRiskMitigationSecuritySharePoint SOA Software Development Software EngineeringStandardsSQL SQL Server StrategicCommunicationsStrategic Planning SystemsEngineeringTechnologyInjectionTesting&EvaluationTLC TrainingTransformation Life Cycle TransportationValidation Verification Web2.0wireless Wargaming
3. Collaboration drivers 23,000 employees 5,000 new hires this year 55%+ On client sites, many on day 1 Geographically dispersed offices Outlook defacto collaboration tool Need easy access to relevant information http://www.flickr.com/photos/sir_mervs/2804845277/ - Sir Mervs
5. SharePoint 2003 Project, team, organizational focus Consolidated Systems One-stop-shop Authoritative Metadata & Taxonomies Access Controlled Accessible vs. Discoverable
6. Challenges & Lessons Learned Search didn’t work Outlook was still easier Didn’t provide for open collaboration Redundant information silos Focus on systems not people There are a number of existing one-stop-shops Learning the hard way - laverrue http://www.flickr.com/photos/23912576@N05/3289897472/
21. Involve core support allies: M&C, L&D, IS, HR, and Legalhttp://www.flickr.com/photos/kiwinz/3386588455/ - kiwinz
22. What works Active and visible executive support. More than messaging, business use. Market as an ongoing campaign well beyond launch Help your champions support your goals Be a visible participant Elevate tactical business uses Change management plan must be agile Incorporate metrics early http://www.flickr.com/photos/rhettmaxwell/2724591849/ - @rhettmaxwell
23. What we need Refocus on the explicit content Integrated document management solution Incorporate the benefits of Enterprise 2.0 methodology into structured projects and team sites Build on the success of Hello, and continue to drive adoption Provide spaces for secured collaboration Simplify knowledge management across the firm Users want one reliable source for information, no matter the structure To-do list book – koalazymonkey - http://http://www.flickr.com/photos/koalazymonkey/3596829214//
24. What we’ll do - 2007 Begin with a clean 07 site Process, clean and migrate 4M documents from 2003 to 2007 Focus on data quality and discoverability for 07 Identify requirements for evolving integrated collaboration system Upgrade infrastructure to improve performance and scalability Continue to leverage FAST across systems for integrated search Ploughing Match – renrut- http://www.flickr.com/photos/treborrenrut/2934770105//
25. What we’ll do - 2010 Selected to participating in TAP Focus on users and feature set for 2010 Migrate ‘clean’ data to 2010 environment Leverage SharePoint as the backend platform that drives the collaboration environment Provide a balanced collaboration system that meets the needs of individuals, as well as organizational structures Integrate existing data and functionality from legacy systems Continue to focus on the individual, they will drive adoption and the overall success of the product Clear Vision – C.P. Storm- http://www.flickr.com/photos/cpstorm/167418602/
26. Lessons Learned in Enterprise 2.0 Obtain leadership buy-in Bring the right people together Develop a shared understanding of the problem Understand the operating environment Develop a customized solution Actively and continuously promote adoption Build communities Evaluate and improve
28. Closing Has to be about people and adoption not the tools Tools have to be flexible and support evolution Data has to be dynamic Data location is not important to your user Obtain leadership buy-in Bring the right people together Develop a shared understanding of the problem Understand the operating environment One size does not fit all Actively and continuously promote adoption Build authentic communities Evaluate and improve
