UNIVERSAL CONTENT MANAGEMENT December 8-22, 2006 University of Minnesota WCM Scoping Agenda.

Slides:



Advertisements
Similar presentations
© 2007 BigVisible Solutions, Inc. All Rights Reserved Coaching Solutions Agile Project Start v
Advertisements

MIGRATION MIGR-09. How to Run Your Next Implementation... Don't Let It Run You! Patricia Johnson Senior Systems Consultant Strategic Systems Group, Inc.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
<<replace with Customer Logo>>
ECM RFP 101 Presented by: Carol Mitchell C.M. Mitchell Consulting.
Internet Management Consultants and Solution Providers Outstanding CMS Projects Lessons from the Front Line.
University of Southern California Enterprise Wide Information Systems Instructor: Richard W. Vawter.
IS 421 Information Systems Management James Nowotarski 16 September 2002.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
Business Intelligence Dr. Mahdi Esmaeili 1. Technical Infrastructure Evaluation Hardware Network Middleware Database Management Systems Tools and Standards.
Project Initiation Meeting Presented By: > > Office of the Chief Information Officer >
Enable Business Intelligence Across the Enterprise William McKnight McKnight Associates, Inc.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
IS&T Project Management: Project Management 101 June, 2006.
Microsoft Office Sharepoint Server 2007 (MOSS) Overview Momentum Microsoft November 15, 2007.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Enterprise Content Management (ECM) Simulator for Return on Investment (ROI)
1 Components of A Successful Data Warehouse Chris Wheaton, Co-Founder, Client Advocate.
Microsoft Office Project Training Materials Jon Jaffe Information Worker Product Managent Group Microsoft Corporation.
> Blueprint Kickoff >. Introductions Customer Vision & Success Criteria Apigee Accelerator Overview Blueprint Schedule Roles & Responsibilities Communications.
Kickoff Meeting Jam 11/18/2011 © Copyright All rights reserved.
Project Management – The Project Charter
Microsoft Office Project Portfolio Server
What is Business Analysis Planning & Monitoring?
GLOCO Enterprise Measurement System Team 4 John Armstrong Ananthkumar Balasubramanian Emily James Lucas Suh May 5, 2012.
1 EDMS 101 Speaker: Monica Crocker, DHS EDMS Coordinator Overview of current project(s) Objective of this section: This session outlines EDMS fundamentals.
Roles and Responsibilities
OFC 200 Microsoft Solution Accelerator for Intranets Scott Fynn Microsoft Consulting Services National Practices.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
 Copyright 2001 Perot Systems Europe. All rights reserved Architecture Model Introduction Tim Taylor.
Roadmap to successful ECM implementation Kateřina Divišová British Chamber of Commerce
U.S. Department of Agriculture eGovernment Program Design Approach for usda.gov April 2003.
PRELIMINARY DRAFT FOR DISCUSSION PURPOSES ONLY Harvard University IT Integration Program – Security Workgroup Kickoff January 5, 2011.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
[PROJECT] PROJECT KICKOFF PRESENTATION MONTH DAY, YEAR.
I Copyright © 2007, Oracle. All rights reserved. Module i: Siebel 8.0 Essentials Training Siebel 8.0 Essentials.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
The Goal: To Climb Above The Competition Copyright 2005: I Lead Projects, L.L.C. Course Description Project Process Workplates Project Process Workplates.
© 2005 IBM Corporation Discovering the Value of SOA with WebSphere Process Integration SOA on your terms and our expertise Building a Services Oriented.
ARCH-04 Before You Begin Your Transformation Project… Phillip Magnay Architect – Applied Technology.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
Planning Engagement Kickoff
Instructional slide to Partner: REMOVE BEFORE PRESENTING TO CUSTOMER
Development Project Dr Kris Welsh Dr Raheel Nawaz.
Office 365 Security Assessment Workshop
Office 365 FastTrack Planning Engagement Kickoff
Document & Web Content Management
SharePoint Governance 101
ServiceNow Implementation Knowledge Management
<Name of Product>Pilot Closeout Meeting <Customer Name>
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Process Improvement With Roles and Responsibilities explained
Description of Revision
SQL Server BI on Windows Azure Virtual Machines
SQL Server OLTP with Microsoft Azure Virtual Machines
Kickoff Presentation Date of Presentation Presenter Name
Machine Learning Session
By Jeff Burklo, Director
Centre name Project Kick Off.
Data Migration Assessment Jump Start – Engagement Kickoff
Core Competencies of a World Class Customer Advisory Board
Employee engagement Delivery guide
Chapter 5 IS630.
Joint Application Development (JAD)
Executive Project Kickoff
{Project Name} Organizational Chart, Roles and Responsibilities
Project Name - Project Kickoff
(Insert Title of Project Here) Kickoff Meeting
Presentation transcript:

UNIVERSAL CONTENT MANAGEMENT December 8-22, 2006 University of Minnesota WCM Scoping Agenda

2 Day 1: Kick Off (December 8 th )  Purpose  Kick-off project and review Goals, Objectives and Success Criteria for the project  Topics  Team member introductions including roles and responsibilities  Overview Enterprise Content Management  Project Goals and Objectives  Project Success Criteria  High Level Scoping Agenda Review  Duration  2 hours  Attendees:  Project Managers  Project Sponsor  Steering Committee  Core Project Team  SMEs

3 Kick Off Agenda (Day 1 – December 8 th ) Topic Start Time End Time LeadAttendees Team member introductionsAAM ECM OverviewAAM Project Goals and ObjectivesRW Project Success CriteriaRW High Level Agenda OverviewAAM

4 Introductions  Please introduce yourself with:  Your name  Your role in the company  Your role on the project  Stellent  Alan Mackenthun – Program Manager  Steve Sommer – Chief Technical Architect  Tim Bergeson – Territory Manager  Doug Brunner – Sales Engineer  University of Minnesota  ?

5 Goals & Objectives (Big Picture)  What are the Primary Drivers of this Project (Ron)

6 Success Criteria  What are the success criteria for this project (examples: TCO reductions, ROI, Time to Market acceleration, etc)  (Ron)

7 Agenda Overview: Scoping Sessions Topics  The Primary Topics for the Scoping Sessions  Day 1 (12/8): Kick-off, Goals & Objectives, Success Criteria  Day 2 (12/11): Project Structure, Process, and Logistics  Day 3 (12/12): Platform Standards and Project Plan Set Up  Day 4 (12/18): Scope Definition: Content Inventory and Requirements Review  Day 5 (12/19): Scope Definition: Architecture and Infrastructure  Day 6 (12/20): Initial Solution Mapping & Work Breakdown Structure Creation (Could be used for additional Content Inventory or Requirements Detail if needed)  Day 7 (12/21): Solution Mapping, Project Planning & Documentation  Day 8 (12/22):Scoping Documentation Review and Wrap-up

8 Scoping Sessions Descriptions  Details for each Session  Purpose of session  Attendees  Suggested duration  Lead for each topic (Person presenting or facilitating session)

9 Day 2: Project Structure, Process, and Logistics (December 11)  Purpose  Communicate project management fundamentals that will be used to manage the project  Topics  Project Organization & Governance  Project Methodology  Stellent Methodology Review  Map Stellent Methodology to Client Methodology  Agree upon methodology for project  Project Logistics  Onsite/offsite, remote access, etc.  Communication Plan  Standard meetings, collaboration tools, issue tracking, etc.  Constraints & Timeline  Assumptions  Change Management  Risk Management  Duration  Full Day  Attendees:  Project Managers  Core Project Team  SMEs

10 Day 2: Project Structure, Process, and Logistics (December 11) Topic Start Time End Time LeadAttendees Kick off: Organization and GovernanceStellentCore Team Project Methodology & StaffingStellentCore Team Break Project LogisticsStellentCore Team Communication PlanStellentCore Team Lunch Constraints & TimelinesStellentCore Team AssumptionsStellentCore Team Break Change Management ProcessStellentCore Team Project RisksStellentCore Team

11 Day 3: Platform Standards & Project Plan Structure (December 12)  Purpose  Detail U of MN platform preferences or standards and set up draft project plan  Topics  Platform Standards  Project Plan Initialization  Plan Training  Plan Testing and Deployment  Duration  Full Day  Attendees:  Core Architecture Team  Project Managers

12 Day 3: Platform Standards & Project Plan Structure (December 12) Topic Start Time End Time LeadAttendees Content Server Architecture Overview Architecture Team U of MN Technical Requirements & Platform Standards Architecture Team Break Draft Project Plan DevelopmentAAM, RW Plan Training Plan Testing and Quality Assurance

13 Day 4: Content Inventory & Requirements Review (Dec. 18 th )  Purpose  Review client’s business requirements and being the process of defining the Stellent solution in enough detail to scope it properly  Topics  Review Inventory of known content  Review Business & Functional Requirements Gathered by U of MN  Attendees  Core Team  Business Sponsor  Technical Leads  CMS BA  Training Lead  Test Lead  Business Users  Duration  Full day

14 Day 4: Content Inventory & Requirements Review (Dec. 18 th ) Topic Start Time End Time LeadAttendees Business & Functional Requirements Review (15 minute Break ~10:00 AM) 8:3011:45U of MCore Team Lunch11:4512:30 Content Inventory  What types of content?  How much of each type?  Formats for input and output?  Workflow needed?  Security (who contributes and who consumes?)  Metadata needed?  How is content contributed and consumed? 12:303:30StellentCore Team Testing & Deployment Requirements3:304:00U of M Core, Testing, System Mgmt Training Requirements4:004:30U of MCore, Training

15 Day 5: Architecture and Infrastructure (Dec. 19 th )  Purpose  Define architecture to be used for Stellent implementation and gather infrastructure related requirements  Topics  Current Architecture  Applied Bio Roadmap for System Usage  Corporate and Application Security Requirements  Database Requirements  Administration Processes  Backup/Recovery and Disaster Recovery  Performance and Availability  Hardware Sizing  Integration and Interface Discussion  Client Attendees & Legend  Core Team  Technical Architect – TA  Network Admin – NA  Unix Admin - UA  Database Admin - DBA  User Admin  Web Dev - WD  CMS Admin - CMS  Duration  Full day

16 Day 5: Architecture and Infrastructure (Dec. 19 th ) TopicStartEndLeadAttendees Current ArchitectureU of MAll U of M Roadmap for System UsageU of MAll BreakAll Database RequirementsStellentCore, DBA Administration ProcessesU of M Core, TA, NA LunchAll Performance (SLAs?) & Hardware SizingStellent Core, TA, NA, UA, IT Availability & Disaster Recovery (SLAs?)StellentCore, TA BreakAll Corporate and App Security Requirements (Active Directory/x500) StellentCore, TA Other Integrations? Architecture PlanningStellentAll

17 Day 6: Initial Solution Mapping / Work Breakdown Structure Development (Dec. 20 th )  Purpose  Analyze business and technical requirements well enough to allow the project to be scoped properly  Final Architecture Review  Begin development of work breakdown structure  Topics  Map business requirements to Stellent solution components such as:  UI Customization, Personalization  Security  Metadata  Contribution  Consumption  Search  Workflow  Scanning  Content Conversion/Migration  Localization  Work Breakdown Structure Development  Client Attendees  Core Team  Duration  Full day

18 Day 6: Initial Solution Mapping / Work Breakdown Structure Development (Dec. 20 th ) Topic Start Time End Time LeadAttendees UI Customization, PersonalizationCore Team SecurityCore Team MetadataCore Team ContributionCore Team ConsumptionCore Team SearchCore Team WorkflowCore Team ScanningCore Team Content Conversion/MigrationCore Team LocalizationCore Team Work Break Down Structure DevelopmentCore Team

19 Day 7: Solution Mapping (continued) & Detailed Project Planning (Dec 21 st )  Purpose  Review scoping workshop results and plan for completion of scoping phase  Topics  Architecture review  Requirements review  Initial solution mapping review  Review open issues  Next steps  Client Attendees  Core Team  Leads  CMS BA  CMS PMO  Duration  Full Day

20 Day 7: Solution Mapping (continued) & Detailed Project Planning (Dec 21 st ) Topic Start Time End Time Lead Attend ees Documentation, Continue Solution Mapping, and/or Architecture Review SS Core Team Project Plan DevelopmentAAM Core Team

21 Day 8: Solution Mapping (continued) & Detailed Project Planning (Dec 22 nd )  Purpose  Complete Scoping Phase Deliverables  Topics  Continued Solution Mapping  Detailed Project Planning  Documentation  Client Attendees  Core Team  Leads  CMS BA  CMS PMO  Duration  Half Day

22 Scoping Review TopicTimeLeadAttendees Architecture Review8:30 – 9:15 Requirements Review9: :15 Initial Solution Mapping Review10:30 – 11:30 Review Open Issues11: :00 Next Steps12:00 – 12: 30 Departure12:30

23 Wrap-up