Standards |
1.Workflows are established for making changes in VISION, documenting those changes, reviewing, and approving changes. 2.The VISION Project has a main active work area that contains the approved JTA, Objectives, and Program—and nothing more. Other work areas are used to house archived nodes such as tasks, objectives, and training units. 3.Archived tasks are removed from the active hierarchy work area and relocated to a separate work area called “Archived Tasks.” 4.Archived tasks include an explanation (no longer performed, subsumed under another task, performed by a different set of workers, etc.) and date of approval to be archived in the Comments field of the task. 5.Archived tasks are unlinked from their objectives, and the objectives are deleted or archived and removed from Training Units, or the Training Units are archived in separate work areas. NOTE: Objectives tested on exams, and Programs delivered in VLS cannot be deleted. 6.Changes to tasks (including changes to elements or SKs) are documented with a comment in the Version Comments field of the task. 7.The Comments field on the General Tab or the Version Tab documents changes to Tasks, Objectives, Questions, or Training Units. The documented changes explain why they are being made. 8.Date tags with explanations are created to mark the date of significant changes to a project’s hierarchies—revising many tasks, learning objects, etc. 9.Recycle bins for any of the hierarchies are used as temporary holding areas until a decision is reached about those nodes. The recycle bins are not permanent repositories of nodes that are no longer part of the hierarchy. 10.Examinations are archived after they are no longer being used. 11.Custom reports no longer used are archived and removed from the Reports lists. 12.Cross Reference Tables show relationships to Vision data that could not otherwise be represented in some other way in Vision. 13.Audit reports show a healthy project devoid of orphans and aliens. |
Best Practices |
•Recognize that any major (or even minor) changes to tasks have ripple effects across all three hierarchies and need to be part of the workflow process. A major change to a task must prompt a review and rewriting of terminal objectives and enabling objectives impacted by KSA and element changes. In turn, test questions and performance evaluations are also impacted as well as the Training Units that contain the learning objects affected. |
