| A | B | C | D | E | F | G | H | I | |
|---|---|---|---|---|---|---|---|---|---|
1 | Priority | Items | Required/Optional | Responsible Party | Description | Blockers | Target Date | Questions | Status |
2 | Server setup and configuration | Required | Jorsek System Administrator | Build and configure server to customer's specifications, configure and validate security, configure backup process. | |||||
3 | Content conversion | Optional (Only required if customer is bringing legacy content into easyDITA) | Customer or Consultant | If content is not already in a .dita format, or requires modification before importing it into easyDITA. | |||||
4 | Import content into easyDITA | Optional (Only required if customer is bringing legacy content into easyDITA) | Customer or Jorsek Customer Success Developer (CSD) | Upload content into easyDITA. If there is a large amount of content to import, a Jorsek representative may assist in this process. | Content Conversion | ||||
5 | Information Architecture (IA) | Required | Customer or Consultant | Analyze existing content and determine what the organization and architecture of the content will look like. | |||||
6 | Define publishing output requirements | Required | Customer | Determine what publishing outputs are needed and what the ouput should look like. | |||||
7 | Develop publishing output transformations | Required | Customer, Consultant, or Jorsek CSD | Develop stylesheets for publishing output transformations. | Define publishing output requirements | ||||
8 | Goal Setting Meeting | Required | Customer and Jorsek Customer Success Manager (CSM) | Determine project goals and timelines. | |||||
9 | Determine primary and secondary contacts on both sides | Required | Customer and Jorsek CSM | Determine who the primary and secondary contact will be on the customer side and on the Jorsek CSM side. | |||||
10 | Schedule recurring meetings | Optional (Some subscriptions do not include regular meetings and training support) | Jorsek CSM | Establish a schedule of recurring meetings during the initial implementation to provide support. | |||||
11 | Develop training plan and schedule training sessions | Optional (Some subscriptions do not include regular meetings and training support) | Jorsek CSM | Define reuse strategy, localization requirements, linking strategy, content library structure, topic types, metadata and taxonomy structure, reports, etc. | |||||
12 | Define assignment workflows | Optional | Customer | Names, steps, multiple assignees, triggers. | |||||
13 | Define file statuses | Optional | Customer | Custom file statuses or colors, commit messages. | |||||
14 | Configure custom assignment workflows and file statuses | Optional | Jorsek CSM | Define assignment workflows and file statuses | |||||
15 | Define localization requirements | Optional | Customer | Target languages, localization tools/formats, workflow. | |||||
16 | Setup localization in easyDITA | Optional | Jorsek CSM | Make sure all necessary languages are available, fonts are uploaded, localization connectors are configured (if necessary). | |||||
17 | Define reuse strategy | Optional | Customer and/or Consultant | Types of reuse, content library structure for reused content. | IA | ||||
18 | Define linking strategy | Optional | Customer and/or Consultant | Types of linking, IA for linking. | IA | ||||
19 | Define conditional processing strategy | Optional | Customer and/or Consultant | Audiences, drop-down list or text box, DITAVals. | IA | ||||
20 | Define versioning strategy | Optional | Customer and/or Consultant | Releases or branching to manage different versions of content. | |||||
21 | Determine Content Library Structure | Required | Customer and/or Consultant | Folder structure for all content, where to store reused content. | IA | ||||
22 | Determine Topic Types | Optional | Customer and/or Consultant | Determine any additional topic types and/or restrictions on the list of available topic types. | IA | ||||
23 | Determine Topic Editor Configurations | Optional (Some subscriptions do not include the Configurable Authoring Interface module) | Customer and/or Consultant | Define element types and any customization to the Topic Editor, if any. | IA | ||||
24 | Define metadata/taxonomy structure | Optional | Customer and/or Consultant | Define structure for taxonomy and metadata and set up in easyDITA. | IA | ||||
25 | Define report requirements | Optional (Some subscriptions do not include custom reports) | Customer and/or Consultant | Define needed reports and develop if not existing. |