Embed Size (px)
DESCRIPTION
University of Minnesota. WCM Scoping Agenda. December 8-22, 2006. 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 - PowerPoint PPT Presentation
Citation preview
UNIVERSAL
CONTENT
MANAGEMENT
December 8-22, 2006
University of MinnesotaWCM Scoping Agenda
2
Day 1: Kick Off (December 8th)
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 8th)
TopicStart Time
End Time
Lead Attendees
Team member introductions AAM
ECM Overview AAM
Project Goals and Objectives RW
Project Success Criteria RW
High Level Agenda Overview AAM
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 SessionsDay 1 (12/8): Kick-off, Goals & Objectives, Success CriteriaDay 2 (12/11): Project Structure, Process, and LogisticsDay 3 (12/12): Platform Standards and Project Plan Set UpDay 4 (12/18): Scope Definition: Content Inventory and
Requirements ReviewDay 5 (12/19): Scope Definition: Architecture and InfrastructureDay 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)
TopicStart Time
End Time
Lead Attendees
Kick off: Organization and Governance Stellent Core Team
Project Methodology & Staffing Stellent Core Team
Break
Project Logistics Stellent Core Team
Communication Plan Stellent Core Team
Lunch
Constraints & Timelines Stellent Core Team
Assumptions Stellent Core Team
Break
Change Management Process Stellent Core Team
Project Risks Stellent Core 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)
TopicStart Time
End Time
Lead Attendees
Content Server Architecture OverviewArchitecture
Team
U of MN Technical Requirements & Platform Standards
Architecture Team
Break
Draft Project Plan Development AAM, RW
Plan Training
Plan Testing and Quality Assurance
13
Day 4: Content Inventory & Requirements Review (Dec. 18th)
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. 18th)
TopicStart Time
End Time
Lead Attendees
Business & Functional Requirements Review (15 minute Break ~10:00 AM)
8:30 11:45 U of M Core Team
Lunch 11:45 12:30
Content InventoryWhat 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:30 3:30 Stellent Core Team
Testing & Deployment Requirements 3:30 4:00 U of MCore, Testing, System Mgmt
Training Requirements 4:00 4:30 U of M Core, Training
15
Day 5: Architecture and Infrastructure (Dec. 19th)
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. 19th)
Topic Start End Lead Attendees
Current Architecture U of M All
U of M Roadmap for System Usage U of M All
Break All
Database Requirements Stellent Core, DBA
Administration Processes U of MCore, TA,
NA
Lunch All
Performance (SLAs?) & Hardware Sizing StellentCore, TA, NA, UA, IT
Availability & Disaster Recovery (SLAs?) Stellent Core, TA
Break All
Corporate and App Security Requirements (Active Directory/x500)
Stellent Core, TA
Other Integrations?
Architecture Planning Stellent All
17
Day 6: Initial Solution Mapping / Work Breakdown Structure Development (Dec. 20th)
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. 20th)
TopicStart Time
End Time
Lead Attendees
UI Customization, Personalization Core Team
Security Core Team
Metadata Core Team
Contribution Core Team
Consumption Core Team
Search Core Team
Workflow Core Team
Scanning Core Team
Content Conversion/Migration Core Team
Localization Core Team
Work Break Down Structure Development Core Team
19
Day 7: Solution Mapping (continued) & Detailed Project Planning (Dec 21st)
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 21st)
TopicStart Time
End Time
LeadAttend
ees
Documentation, Continue Solution Mapping, and/or Architecture Review
SSCore Team
Project Plan Development AAMCore Team
21
Day 8: Solution Mapping (continued) & Detailed Project Planning (Dec 22nd)
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
Topic Time Lead Attendees
Architecture Review 8:30 – 9:15
Requirements Review 9:15 - 10:15
Initial Solution Mapping Review 10:30 – 11:30
Review Open Issues 11:30 - 12:00
Next Steps 12:00 – 12: 30
Departure 12:30
23
Wrap-up
