From the initial stages of the design of a course to the go-live of that course with students, there can be many tasks to complete in Realizeit, involving potentially numerous team members. Workflows have been introduced in Realizeit to help manage and track the entire course building process.
Roles can be defined, e.g. Project Manager, eLearning Architect, Course author, with varying customizable rights to the tasks and artefacts.
Artefacts are used to track any files that will be associated with the process, for example initial design documents, or source materials for the content of a node.
Tasks are established for each stage in the process, e.g. create the curriculum, review content, version course. A process role should be associated with the task to identify the responsible individual(s). A due date for a task can be implemented using an offset from the project start date. Certain activities are available for association with the task to streamline the execution of that activity, e.g. click on a button to create the curriculum definition, click on a button to start creating the questions.
Multiple instances of a task can be created for each curriculum activity, e.g. if 15 nodes are envisaged for the curriculum, then 15 instances of the “Ingest lesson” activity can be created, i.e. one for each node. Relationships between artefacts and tasks can be established. Conditions and outcomes can be used to create dependencies between tasks. For example, a task cannot be created in the workflow until another prerequisite task is completed. An outcome can be used to prompt another task. There can be multiple outcomes for a task, e.g. “Accepted” and “Revisions required”. Notes can be recorded against the tasks.
An institution can create a process template to be used globally for all courses or a subset of courses (e.g. for all environmental science courses). This template identifies the roles, artefacts and the tasks associated with the process. Then a project can be created for a particular course, and the process template can be used as the basis for that project.
Each user associated with a project will see the Workflow dashboard icon upon login. From here, tasks for all relevant projects can be viewed. The user can filter this to a specific project. Once a task is complete, the responsible party can mark it as done. If an artefact is required for a task, the user is prompted to upload the file. According to the outcomes, new tasks are created and made visible to the relevant individuals.