University of Minnesota

1. University of Minnesota WCM Scoping Agenda December 8-22, 2006

2. 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 Day 1: Kick Off (December 8th) • Duration • 2 hours • Attendees: • Project Managers • Project Sponsor • Steering Committee • Core Project Team • SMEs

3. Kick Off Agenda (Day 1 – December 8th)

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. 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 Day 2: Project Structure, Process, and Logistics (December 11) • Duration • Full Day • Attendees: • Project Managers • Core Project Team • SMEs

10. Day 2: Project Structure, Process, and Logistics (December 11)

11. 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 Day 3: Platform Standards & Project Plan Structure (December 12) • Duration • Full Day • Attendees: • Core Architecture Team • Project Managers

12. Day 3: Platform Standards & Project Plan Structure (December 12)

13. 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 Day 4: Content Inventory & Requirements Review (Dec. 18th)

14. Day 4: Content Inventory & Requirements Review (Dec. 18th)

15. 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 Day 5: Architecture and Infrastructure (Dec. 19th)

16. Day 5: Architecture and Infrastructure (Dec. 19th)

17. 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 Day 6: Initial Solution Mapping / Work Breakdown Structure Development (Dec. 20th)

18. Day 6: Initial Solution Mapping / Work Breakdown Structure Development (Dec. 20th)

19. 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 Day 7: Solution Mapping (continued) & Detailed Project Planning (Dec 21st)

20. Day 7: Solution Mapping (continued) & Detailed Project Planning (Dec 21st)

21. 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 Day 8: Solution Mapping (continued) & Detailed Project Planning (Dec 22nd)

22. Scoping Review

23. Wrap-up Questions?