The first time we tried to apply Agile Kanban to a project, we went overboard and added a Kanban visual card (sticky note) for everything. We had too many cards. It frustrated our first team.

Of course, this was not the best idea. Over time and with many instructional/LX designers providing input, we have currently settled on tracking the following things for courseware with significant software code.

  • Deliverables

    • CDD (if required)

    • Prototypes

    • Courseware Package or Instructor Support Package

  • Lesson Level Work Items

    • Lesson 1

    • Lesson 2

    • Lesson 3, etc.

  • Learning Objective (LO) Component Level Work Items

    • LO 1.1 text

    • LO 1.1 media

    • LO 1.1 test items

    • LO 1.2 text

    • LO 1.2 media

    • LO 1.3 test items

    • et cetera

  • Task Level Work Items

    • Risk mitigation tasks

    • Quality tasks

  • Change requests (CRs) / Defects

For projects with significant software code, like simulations and game engine work, user stories and epics are more appropriate work items because the practitioners are more often software developers than training professionals.


Line By Line

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

Back to Overview