1 Nile (Plone) SDT Review 6/6/06 Version.02, 5/25/06 DRAFT 2 SDT Process Context We are here. 3 Purpose Provide an introduction to Content Management Systems (CMS) and other collaboration tools Provide overview of Nile/Plone activities and resources to date Request SDT Approval for continuation of Nile Production Readiness Project Request additional resources and servers for successful production launch and continued deployment of Nile 4 Content Management and Collaboration Tools Overview 5 Strategic Importance Actions: Four priority areas (the "Big Four") will be implemented in 2006: Customer Service Communications Project & Financial Management Reliable & Responsive System 6 Related Tools Definitions Wiki A wiki is a type of website that allows users to easily add and edit content directly in the web browser. In its purest form, a wiki is a flat, egalitarian environment: if you can read something, you can edit it. This makes it very easy for users to be contributors, which can result in content which is much more likely to be dynamic, current, and useful. A wiki is text- oriented; many of them allow "attachments", but they are generally not designed for management of arbitrary documents. Most wikis support version control, so that accidental changes or vandalism can be easily replaced with an earlier copy; this eliminates user apprehension about "breaking something" and increases everyone's comfort level with the once-radical concept of the consumer-as-creator. Many wikis these days have rich support for access control, but this type of tool is best suited for freeform collaboration. Blog A blog resembles an electronic diary. It collects entries which are not meant to be edited after they are created, and displays them in chronological order. Besides individual therapy, this format is also useful for meeting minutes, and for published logging of procedures and processes of all types. Some shops even use them as a modern system manager's notebook, to track system changes. Some blog software supports the addition of comments to existing entries, and may allow filtering of content for various presentations by date, category, author, or other attributes. Permissions and access control vary by product. Document & content management systems Traditionally, a document management system supported and controlled the storage, version control, and modification of a variety of different files and documents, including presentations, word processing documents, and spreadsheets. This is a more sophisticated and accessible approach to the old, inflexible, shared-filesystem approach, which made it difficult to prevent multiple attempts to edit a document and to track changes. Today, the line between documents and other types of content, such as HTML, has been blurred. Content management systems can typically provide tracking and version control not just on HTML, but also on documents such as presentations and spreadsheets. Similar to document focused systems, strict access control and document version control can be core feature sets of content management systems. In addition, content management systems typically seek to provide a structure for supporting web publishing workflow; they usually support specific roles, such as authors, reviewers, and site editors. An important feature of such systems is the separation of content creation and editing from graphic look and feel. Based on information from: https://depts.washington.edu/cacwiki/pmwiki/pmwiki.php?n=Main.Descriptions 7 Collaboration Product Examples MediaWiki A true wiki, perhaps the one best known to most people (even if its name isn't salient) because it powers Wikipedia, a hugely successful community-driven information resource.Wikipedia Confluence Confluence is a commercial wiki which offers enterprise support. The existence of a commercial product such as this is evidence of the growing appreciation of the business benefits of this type of tool. WordPress WordPress is "blogging" software with an emphasis on accessibility and usability. Plone Plone is a feature-rich content management system. It also supports document management, and can meet a wide range of collaboration needs. SharePoint Originally a document management system, Sharepoint has become Microsoft's collaboration platform, and can now function as a content management system for web publishing, as well as supporting the addition of wiki-type tools within sites. Its primary advantage for some user groups is tight integration with other Microsoft products. This is not currently available as a C&C-wide service; technical and security issues need to be resolved before this happens. Excerpted from: https://depts.washington.edu/cacwiki/pmwiki/pmwiki.php?n=Main.Descriptions 8 Nile Description Nile is C&Cs implementation of Plone and other third-party open source products 9 Nile Project Overview 10 Nile Oversight Group & Sponsors Oversight Group Alisa Hata Terry Gray Cindy Brown Scott Mah Sandy Moy Sara Gomez Lori Stevens Oren Sreebny Sponsors Terry Gray Sandy Moy 11 Historical Background Plone was selected out of a field that included: Collaboration tools: SharePoint, Catalyst Content Management tools: eZ Publish, and Open CMS Plone pilots (including DRBR) were deemed successful and no show stoppers were identified Currently, Team is preparing tool for wider availability 12 Nile Production Readiness Project Objective: This project, currently underway, will define and document key processes, guidelines, templates, tool functionality, and support structures to adequately prepare the tool for production launch, including preparing a: Defined scope of the Plone offering to the customers identified for the next phase of implementation Defined and documented Plone support model Defined and documented key support processes for efficiently and effectively managing Plone Trained and prepared support staff to handle larger volume and complexity of customer demands Defined and documented key user and support guidelines Developed and documented definitions for key content management and Plone Defined and documented key system user help content Implemented key system features Prepared for deployment to upcoming customer segments 13 Current Nile Staffing Resources NameRoleOriginating Group% on Project Tamara AusterladeProject ManagerTechnology Engineering Project Management & Support Services 25% Melody Winkle Tier 1 & 2 Support New Customer Outreach New Site Set-up and Refinement Technology Engineering Project Management & Support Services 90% Ginger Brower Nile Support Site Architecture Training Development and Delivery Technology Engineering Project Management & Support Services 90%* (*Currently on leave) Kent Kurth Tier 3 Support New product investigation Troubleshooting SDS Software Support Group80% Frank Poloney (contractor) Help Content Permissions/Workflow Requirements Technology Engineering Project Management & Support Services 50% Extended Project Team NameRoleOriginating Group% on Project Kathi Woods CACTools User Liaison Help Content Editor Communications20% Frank FujimotoNile System AdministratorSDS Collaborative Platforms Less than or equal to 10% Core Project Team Current Total: 2.X, Down from 4.5 (excluding leave participant) 14 Existing Project Resources 15 Nile Deployment Plan 1 st Quarter 062 nd Quarter 063 rd Quarter 064 th Quarter 061 st Quarter 07 Customer Segment Angel Users Select Project Teams Focus Groups New Steering Committees CacTools Phase I Requirements Definition 16 Current Nile Customers 17 Existing Nile Tiered Support 18 Deployment Costs People Have: 2.65 Need in addition: 25% Project Manager 50% Instructional Designer & Trainer 50% Business Analyst 50% Information Architect Back-Ups for Tier 1-4 Hardware Back-up Server Test Server 19 Ongoing Costs CACTools Deployment People: 8 20 Ongoing Costs Staff Breakdown May- 06 Jun- 06Jul-06 Aug- 06Sep-06 Oct- 06 Nov- 06 Dec- 06 Jan- 07 Feb- 07 Project Manager 25% 50% 90% Business Analyst, Outreach 0% 50% Information Architect 0% 50% 90% Tier 1 & 2 Primary 90% Tier 1 & 2 Back-up 0% 50% 90% Technical Writer 40% 80% Instructional Designer/Trainer 0% 50% Application Support, Primary 80% Application Support, Back-up 0% 50% 80% System Administrator, Primary 10% System Administrator, Back- Up 0% 5% CACTools Liaison 20% 50%90% 21 Ongoing Costs for Staff 22 The Good News No anticipated additional hardware or equipment costs once test and back-up server installed!* *Need to verify 23 SDT Decisions Needed 1. Decision to continue Nile Production Readiness Project: Approve Reject Other:___ 2. Decision to add additional resources to Production Readiness Project Approve Reject Other:___ 3. Decision to increase resources for CACTools deployment Approve Reject Other:___ 24 Non-Nile Communication/ Collaboration Resources NameRoleOriginating Group% Dedicated