Presented by Karuana Gatimu, ECM P February 18, 2009

Technology professional with 18 years experience in project management, custom application development and corporate training. Certified Enterprise Content Management Practitioner Currently IT Project Manager & SharePoint Architect for Skechers USA, a global footwear manufacturer 10 Years as a content management specialist for legal and government industries Principle Enthusiast at SharePointStrategist.com

 Focus on Technology as a Service  Start the Conversation – Engage Others  It’s a Process not a Product  Evaluate Existing Systems & Processes  Find Your Pain Points What Is It? An ECM Strategy document is an iterative document which outlines your requirements, approach & measurable goals for delivering ECM services to the enterprise.

 Understand Your Process: Whether you use the SDLC, MSF, RUP or a hybrid have a project management process  Establish Project Stakeholders: These executive level people will help you manage organizational change  Establish a Communication Plan! Know in advance how you will communicate about your project  Plan your Resources: Yes, even if you are a team of one have a resource plan  Define Success: Find measurable goals and track your success. Create a feedback process for your users

Docs/tasks/calendars, blogs, wikis, integration, project management “lite”, Outlook integration, offline docs/lists Enterprise Portal template, Site Directory, My Sites, social networking, privacy control Enterprise scalability, contextual relevance, rich people and business data search Rich and Web forms based front-ends, LOB actions, pluggable SSO Server-based Excel spreadsheets and data visualization, Report Center, BI Web Parts, KPIs/Dashboards Integrated document management, records management, and Web content management with policies and workflow Content Management Business Process Business Insight Collaboration Portal Search

Business Value

Initial Defined Managed Measured Optimizing Body of Work Reference: Carnegie Mellon SEI

ECM StrategyTechnology as a ServiceArchitecture DesignIT ResourcesPilot Project SelectionRisk AnalysisBest Practices Implementation

 If you are new: ◦ Think about an appropriate pilot project to cut your teeth on ◦ Do not over commit or deploy all features at once  If you have an existing deployment: ◦ Which segments can you enhance? ◦ How are you delivering value to your users? ◦ Which pieces of the strategy have you missed on previous projects & how can you improve?

 Taxonomy - How you classify data as expressed through: ◦ Content database & web app design ◦ Content types ◦ Custom columns ◦ Other metadata  Legacy Integration ◦ Links to external databases (CorasWorks Tools)  Data Conversions ◦ Unstructured to Structured Data ◦ File Stores

Microsoft

MYSite (Main Persona - Redesigned) CalendarContactsTasksDocuments Department or Workgroup Dept. Calendar Shared DocsE-Forms Resources Master vendor & employee lists Custom DB connections External Links Published Documents Centrally Configured Security Profiles via AD Load balanced at site level Visibility by Target Audiences

 The solution to serving up information from disparate systems  Embodies the idea of technology as a service to the enterprise by allowing users to focus on business issues not technology  True integration of the capture and consumption of information  The “X” Factor  Breeze by CorasWorks

 CorasWorks is an application development tool  The Power: ◦ Minimizes need for custom code or.NET developers on staff  OOTB Web Parts, Wizard driven configuration, easy Admin screens ◦ Data Integration Toolset pulls and pushes data to/from external sources  The Flexibility ◦ Allows documents & lists to be viewed and acted upon across sites & site collections  Roll Ups & Action Libraries ◦ 80% of all central configuration, design and deployment can be automated  Gallery Management, Central Configuration, Global Navigation

 a. SOX  b. HIPPA  c. Information retention policy ◦ Document & data life cycles  d. Legal (litigation & other requirements)  e. Executive management review/approval  f. Enterprise change management policy Each consideration can be handled by content types with associated workflows, audit trails, publishing sites, content expiration and a taxonomy that identifies the owners of content.

Fire Drill Schedules & Emergency Procedures Backup & Maintenance Plans Hardware/Software levels Gain & maintain the trust of the enterprise to reliably safeguard their data

Immediate and future needs Amortized costs Hardware, licensing, service expenses

ResourceAllocation Education of Internal Resources Balance Internal & External Expertise Long Term Planning Institutional Knowledge Management

Pilot Project Selection Define Business Case BudgetRiskAdvisePlan

 Goals by Quarter for MBO planning ◦ Be careful what you publish!  Quality Assurance & Measuring ◦ a. User feedback process ◦ b. Revision criteria ◦ c. Defined criteria for success ◦ d. Iterative development processes ◦ i. Prioritize feature roll outs by iteration

 CorasWorks’ Breeze Virtual Workplace: Use this powerful tool to educate your teams on functionality and stimulate your imagination about solutions. CorasWorks’ Breeze Virtual Workplace  Global Networks: Assistance from professionals who have seen a variety of system implementations is critical. Global Networks  Web Resources: ◦ Microsoft ◦ CorasWorks.net ◦ SharePoint University SharePoint University ◦ SharePointStrategist.com SharePointStrategist.com  Must Have Books: ◦ Essential SharePoint 2007 by Jamison, Carderelli & Hanley ◦ Microsoft® Office SharePoint® Server 2007 Administrator's Companion by Bill English ◦ SharePoint Best Practices by Bill English