Software development is able to automate testing of code to aid the team.

In learning experience development, there are a few things we can automate, but much of the training product quality assurance content checks are still performed manually by hand. Quality criteria vary by organization, so the following table is not exhaustive, but illustrative.

Table 1. Quality Testing
Manual (by hand) Automated

Instructional quality criteria

Textual content spell check

Accessibility quality criteria (section 508)

Some grammar checking of textual content

Security requirements

Interactivity software code tests

Meets learning objectives from the CDD

SCORM conformance

Assessment and measurement

Nothing automated yet

Usability of the learner interface

Nothing automated yet

Functionality of eLearning interactivity or blended components

Nothing automated yet

Game or simulation mechanics, pacing, balance between engagement and pedagogy

Nothing automated yet

To help ensure that the customer is getting a consistent quality experience, use content checklists and functionality test cases performed by QA before delivery to the customer.

We suggest implementing checklists for Course Design Documents (CDDs), Prototypes, etc. Consider including a link to the checklist in your definition of done card that sits at the top of the CDD Done column or the Prototype Done column.

We recommend a book called, The Checklist Manifesto: How to Get Things Right, by Atul Gawande, January 4, 2011. Apply it for quality for WIP. If checklists work for Pilots and Medical Doctors, then they can also work for learning experience development.

You also may need to convince your organization’s quality experts to think differently about how to prove we use Lean-Agile the way we say we do. Many of these folks approach the world with a records view and will want written record artifacts for proof. Often, these staff are familiar with traditional tools like meeting minutes and forms, but not Kanban cards. So you may need to convince these folks that the time-date stamp functionality in virtual Kanban cards activity logs are records sufficient to prove that we do what we say. Various virtual Kanban suppliers have a similar functions. Find ways like this to reduce transactional waste and keep your project more Agile and Lean than just saying okay to whatever they require might get you. This is part of your change management process when selling Lean-Agile in your organization.

Many quality specialists have more experience with traditional or waterfall approaches to project management where often the quality checking is all done near the end of the project lifecycle rather than during each process step along the way and leveraging the "definition of done." Lean-Agile can be a big change to people in the quality field too.

Line By Line

Here a Little, There a Little, Layer by Layer.

Back to Overview