Let’s reuse the example course in the following figure to discuss a courseware initial plan.

WhyIncrement
Figure 1. Courseware Example Scope

For this example, if you assume that figure depicts the courseware scope, then the courseware initial plan would look like the following.

Note
Agile in software development calls the initial plan a release plan. We will call it a Courseware Initial Plan.

Course name: XYZ Course

  1. Iteration 1

    • Courseware Increment #1 will include LOs 1–10.

  2. Iteration 2

    • Courseware Increment #2 will include LOs 11–20.

  3. Iteration 3

    • Courseware Increment #3 will include LOs 21–30.

  4. Iteration 4

    • Courseware Increment #4 will include LOs 31–40.

It doesn’t need to be any more complicated than this. We have used this level of detail with external customers.

You can then take this plan to the customer as the high level or initial plan. Be sure they know that iteration planning meetings may need to shift LO scope around to adjust to changing circumstances and unexpected events.

Iteration #1 will have a planning meeting that will result in an iteration goal that commits to a particular scope. If nothing changes in this example, that scope goal message to the customer will simply state, "LOs 1–10 will be completed during iteration 1."

Image

Line By Line

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

Back to Overview