Historically, training development has addressed chunks of a course as the course, or as lessons. Some might wonder why we can’t just use these familiar handles to talk about the courseware.

We have used the following figure to show customers how the entire course is too large of a batch size. It graphically shows that even lessons tend to vary in length and do not support the Lean idea of consistent flow through our development system. LOs vary in size too, but they are more often similarly sized than lessons, so we have decided to use LOs as the work item level in our product breakdown structures. It is good enough and both the training teams and the customers grasp it quickly.

Agile, in our Scrumban style, fixes the schedule to two-week increments so the time does not vary, but the scope may vary. In this example, we have fit a certain number of LOs into a single iteration, so that becomes the batch size. So what do you call that? Agile calls it a product increment. So we’ll call it a courseware increment. That gives us a handle with which we can address this chunk of the course in our communications with each other and with the customer stakeholders.

WhyIncrement
Figure 1. Agile Increments are Similarly Sized vs. Lessons

The things delivered each iteration include:

  • Iteration Goal (scope commitment)

  • Each LO storyboarded and developed

  • Increment Test Bank

  • Fix Change Requests

  • Iteration Review/Demo (inspection & evaluation) in a synchronous meeting

Image

Line By Line

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

Back to Overview