Changes between Version 2 and Version 3 of Public/StartPagePlanningWorkflow


Ignore:
Timestamp:
Sep 18, 2020, 8:18:43 AM (16 months ago)
Author:
Boris Horner
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Public/StartPagePlanningWorkflow

    v2 v3  
    1111* If the plan changes, the planning person must actively notify the other contributors that they should check the updated Excel sheet.
    1212* Completion of work items must actively be documented by users in the Excel sheet.
     13* Even if changes are tracked in Excel, the information is rarely up to date. It is difficult to predict in-time completion based on this.
     14
     15Even though it might be the same person performing both logical steps, planning and authoring, and even though the planner / author might join both to one practical step, both are different actions and require different perspectives. When conceiving a new documentation product, the planner should identify the existing modules and media assets (e. g., based on metadata), and decide for each node in the documentation to be written:
     16* to re-use an existing item without further changes,
     17* to version an existing item and apply the additions to content and metadata in the new version,
     18* to copy and modify an existing item, or
     19* to create new content from scratch.
     20
     21Only with an overview perspective, the planning task can be performed with optimal re-use and information architecture.
     22
     23When the document structure and the required actions for each node are decided, the planner documents them.
     24* In an Excel approach, all modules are written into the table, and information about the creation process, the responsible author and any background information and metadata already known on planning level are added to the rows. Next, the planner creates the items in the Component CMS and adds a reference to them in the Excel sheet. The authors must pick the information they need from the Excel sheet and enter any further info and the completion status. All of this is manual. Particularly when review / modification cycles occur, this tends to become obscure.
     25* In a workflow approach, the planner builds the document with links to new and re-used items and adds all planning information and task assignment directly to the nodes. The workflow system cares for all other management:
     26 * It sends work items to authors, node by node.
     27 * Once an author completes a work item, the assigned review person is automatically notified.
     28 * The reviewer adds any comments to the workflow item and optionally may add comments into the (PDF or HTML based) review document.
     29 * The reviewer decides whether to reject or accept the work item.
     30  * In case of rejection, the work item is sent back to the author with all comments or notes.
     31  * In case of acceptance, the work item is propagated to a //released// state.
     32 The workflow system not only tracks the work items, but also their statuses, and in consequence, changes the permissions so that current stakeholders can do their work but nothing else.
     33
     34The advantages:
     35* Users do not need to care about documenting their changes.
     36* The completion status of any node is always known, thus, predictions whether completion in time is realistic are much easier.
     37* No work items get lost.
     38* Changes in the planning are immediately mirrored in the data and workflow. Obsolete tasks are withdrawn.
     39* Due to the explicit planning step, re-use planning is from a global perspective and thus leads to higher re-use rates and better quality and integrity.
     40
     41== What we can do for you
     42* Together with you, we analyse your information logistics and processes and conceive an automation suiting your existing Component CMS.
     43* Depending on CCMS vendor policies, we implement the process automation ourselves or collaborate with the vendor.
     44* Even though software system vendors offer the conception of such processes, too, they tend to be too focused on their own product. This is particularly relevant, when multiple information systems are connected and the processes touch more than one of them. For example, if a PIM system, a CCMS and a spare parts catalogue share data and the authoring process steps are interlinked. We know these system categories well and conceive workflow automation that integrates these systems.