1 / 41

Interlab 2003 November 6, 2003

Interlab 2003 November 6, 2003. DOE’s Implementation of a CMS for Energy.gov. www.energy.gov. Getting from here…. …to there. The Task. Redesign Energy.gov Reorganize Site Content Improve Search Engine Implement a Content Management System Implement a Taxonomy

tiger-carter
Download Presentation

Interlab 2003 November 6, 2003

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interlab 2003 November 6, 2003 DOE’s Implementation of a CMS for Energy.gov

  2. www.energy.gov Getting from here… …to there.

  3. The Task • Redesign Energy.gov • Reorganize Site Content • Improve Search Engine • Implement a Content Management System • Implement a Taxonomy • Plan for a roll-out to other DOE entities

  4. The Plan • Get DOE Buy-in • Define Roles and Responsibilities • Establish Technical Infrastructure • Create templates / pages • Develop / Convert Content • Develop a Taxonomy • Implement / Test / Deploy

  5. The Plan 1. Get DOE Buy-in • The Committee • 34 DOE staff members representing a cross-section of the organization • Questionnaires • Initial planning sessions • Responses: • Support • Indifference • Skepticism • Enthusiasm • Hostility

  6. The Plan 2. Define Roles and Responsibilities • Create a Content Team • Working Relationships: IT / Multiple vendors • Management v. Web Staff • CMS is a New Animal: Who’s Who? • Decision-makers

  7. 3. Establish Technical Infrastructure Requirements Web Server Application Server Database CMS Software Search Engine Test / Staging / Production Roles and Responsibilities Acquisition of HW / SW The Plan

  8. 4. Develop Templates / Pages The Plan • Magic! • Magic…?

  9. 4. Develop Templates / Pages The Plan • Magic…? • Programming • HTML Templates • JSPs • Wiring to Admin / Authoring Engine • Wiring to Display Engine

  10. 4. Develop Templates / Pages The Plan • Content Management Wiring • Templates • Content “Chunks” • Users • Authors, Editors, Approvers, Admins • Workflows • Steps in the Publishing Process

  11. LAYOUTS TILES - “Content Containers” - Reside within Layouts - Page or section-specific - Reusable • Some have editable “behaviors.”

  12. Group tiles to use with Workflows Workflows relate to groupings of content LAYOUTS TILES Author 2 Workflow 2 Author 3 Workflow 3 Author 1 Workflow 1

  13. The Plan 5. Develop / Convert Content • “Moveable” Content • New Content • Disposable Content • Formats and Formatting • Automating Conversion

  14. Content Plan 6. Develop a Taxonomy • What is a Taxonomy? • Office of the CIO Taxonomy • “A to Z list” • Topics • Offices and Facilities

  15. The Plan 7. Implement / Test / Deploy • Roles and Responsibilities • Testing • Functional • System • Regression • Stress • Acceptance • Deployment: An Environmental Concern • Testing / Staging / Production

  16. Executing the Plan • Redesigned the Site • Got DOE Buy-in • Wired the Templates • Developed a Taxonomy • …? Develop / Convert Content

  17. Executing the Plan IT Words to Live By: • Expect the Unexpected • Plan for Failure

  18. Executing the Plan • Redesigned the Site • Got DOE Buy-in • Wired the Templates • Developed a Taxonomy • …? Develop / Convert Content

  19. Executing the Plan • Redesigned the Site • Got DOE Buy-in • Wired the Templates • Developed a Taxonomy • …? Develop / Convert Content • No Web team established (Cost not built into project) • Dependence on others caused delays • No plan for automating conversion

  20. Executing the Plan • Redesigned the Site • Got DOE Buy-in • Wired the Templates • Developed a Taxonomy • …? Develop / Convert Content • …? Define Roles and Responsibilities • …? Establish Technical Infrastructure…

  21. Executing the Plan Remember…: • Expect the Unexpected • Plan for Failure

  22. Executing the Plan Establish Technical Infrastructure • Acquisition of HW / SW

  23. Executing the Plan Establish Technical Infrastructure • Acquisition of HW / SW

  24. Executing the Plan Establish Technical Infrastructure • Acquisition of HW / SW

  25. Executing the Plan Establish Technical Infrastructure • Acquisition of HW / SW

  26. Executing the Plan • Redesigned the Site • Got DOE Buy-in • Wired the Templates • Developed a Taxonomy • Develop / Convert Content • …? Define Roles and Responsibilities • Establishing Technical Infrastructure delay = • System Configuration delay • CMS Software Deployment delay • Training delay • Content Entry delay

  27. Executing the Plan • Redesigned the Site • Got DOE Buy-in • Wired the Templates • Developed a Taxonomy • …? Develop / Convert Content • …? Define Roles and Responsibilities • Establish Technical Infrastructure • Implement / Test / Deploy

  28. Executing the Plan Murphy’s Law: • Program Manager Change Shortened Deadline • Timeline Crunched • Content Creation Fell Behind, Delaying Testing • Other IT Projects Demanded Resources • The Site Launched …

  29. Executing the Plan Murphy’s Law A driver incompatibility between application server and search software… …the site was slow due to connection pooling issues…

  30. Executing the Plan Murphy’s Law A high-visibility public site with multiple players and something goes wrong… • …? Define Roles and Responsibilities • Fingers Pointing • Hands Wringing • Too Many Fingers In the Pie • Multiple Solutions Tried • Testing Needed • IBM, Oracle Contacted…

  31. Executing the Plan A driver incompatibility between application server and search software… …was resolved.

  32. Executing the Plan • Redesigned the Site • Got DOE Buy-in • Wired the Templates • Developed a Taxonomy • Developed / Converted Content • Defined Roles and Responsibilities • Established Technical Infrastructure • Implemented / Tested / Deployed • Launched and Relaunched

  33. Executing the Plan

  34. Lessons Learned • Manage Your Project • Be a Team • Give Too Much Time to Content Conversion • Know Your Software • Clarify Roles and Responsibilities • Document Everything • Expect the Unexpected • Plan for Failure

  35. Lessons Learned Manage Your Project • Set Reasonable Goals • Use a Phased Approach • Regard Each Project Element As a Project • Can My CMS Make My Coffee? • Be a Team

  36. Lessons Learned Give Too Much Time to Content Conversion • Analyze Your Content Carefully • Be Ready To Jettison Outdated Content/Methods • Look for Automated Conversion (*but be careful) • Clarify Roles And Responsibilities • Staff Up To Handle The Job

  37. Lessons Learned Know Your Software • What’s New? • How Will This Change Our Processes? • Be Sure Your Vendor Can Tell You What Is Really There • Exception Handling

  38. Lessons Learned Clarify Roles and Responsibilities • Decision Makers • Publishing Staff, Authors, Admins • System: Staff, IT, Vendors • Figure It Out Up Front • Communicate Weekly (at least!) • Document Everything

  39. Lessons Learned Document Everything • Statements of Work (SOW) • Change Control • Roles and Responsibilities • Technical Documentation • Training • Updates and Upgrades

  40. The Good News It Works… …If You • Manage Your Project • Expect the Unexpected • Plan for Success

  41. Interlab 2003 November 6, 2003 A CMS for Energy.gov

More Related