New ELU Projects Design and QA Model

New ELU Projects Design and QA Model

1. Analyse

   • Identify the content SME (1) and editorial SME (2)
     • Testing and Quality Assurance strategy agreed between the ELU and the SME
       • Project schedule and project milestones are agreed between the ELU and the SME. Please refer to ELU Project Tracer
   • Design
     • Storyboard is produced by the Instructional Designer
       • Look, feel and tone of the resource is finalised including the creation or sourcing of digital assets (videos, audio, interactivities as well as graphics, icons and imagery drawing from ELU Brand Toolkit)
         • Structure and navigation is finalised
           • Quality assured by Head of Digital Education
             • Changes needed?
               • Yes
                 • Changes are applied by Instructional Designer and project is resubmitted to HDE
               • No
                 • Storyboard is sent to SME for QA against the learning objectives, approval and sign off
         • Consider potential accessibility issues
     • Course mock up for DELTA is desiged
       • Course is set up on DELTA.
     • Develop
       • SME Provides final version of the content
         • Content is being proof read and signed off by the second SME
           • Content is QA and signed off by the HDE
       • Resource is developed using a three-stage Quality Assurance model which allows feedback and amendments through the process
       • Implement
         • Evaluate
           • User survey is designed to measure resource quality and user satisfaction
           • User data will be collected from DELTA to identify crucial content updates and elements causing issues
             • Suggest Improvements
         • If necessary communications are issued to increase user engagement and increase participation
         • Make live
         • Run with a pilot group first if needed
         • Provide training if needed
         • Identify and log the long term review schedule
           • Who? When? What?
         • Store and document all assets (e.g. source files) used
       • Create first version of the resource
         • Alpha test by Instructional Designers: content
           • Spell check, grammar and punctuation
           • Language
           • Consistency: fonts, colours etc.
           • Branding
           • Apply necessary updates following Alpha and retest
             • Beta test by Digital Systems Officer: functionality
               • Accessibility
               • Device compatibility
               • Stability across different devices and operating systems
               • Apply necessary updates following Beta and retest
                 • Final review from user experience viewpoint by HDE, SME and DEALers
                   • Apply necessary updates following final review and retest
           • Copyrights and referencing
     • Initial version of content is provided by the SME
   • Target audience
     • Gaps in knowledge and skills
       • Learning Outcomes
         • Learning interventions
           • Structure, flow and tone of the resource is agreed

2. 6/2/2019

3. Kick of Phase

   • Project team is established
     • Project objectives are defined
       • User agreement is drafted
         • Communications strategy is being agreed
         • Content schedule is agreed
   • Project content is identified