In one situation where we needed to have the staff for a customer not using Lean-Agile to be conversant with it so when they moved from that project and back to a Lean-Agile customer they could help, we decided to have even the traditional ADDIE waterfall team use a Kanban board in addition to their normal process.

This customer was unaware we were using it in-house because we did not show it to them.

We set up the columns differently than the Lean-Agile board because for this project the storyboard was for an entire lesson at a time and the entire course had to be storyboarded before we could move into any development.

We also did not have Scrum fixed iterations on this team, but used the Kanban board to see the progress towards the traditional courseware schedule milestones on the Gantt chart.

Guess what we learned?

The Kanban board and the daily stand-up synchronization meetings of 15 minutes maximum still helped keep the team better coordinated.

It did not help as much during the CDD development because the instructional/LX designers felt they already knew what they needed to do and the Kanban was additional overhead work to them. However, it helped us see where multiple teams were with the work in process at a glance, so we asked them to do it for our benefit rather than for theirs. They did, albeit some in a grumpy way initially.

When we got to storyboarding and the authoring tool and experts had to come aboard the team to get the ID’s vision into the tool, it helped more.

After that, when we went into that customer’s "developed lessons" stage, it helped just as much as on the Agile teams because everyone involved could see what was going on.

Overall, we recommend using Kanban for just about any team doing work. The only time it may not be worth it is when the team only requires one person for a time.


Line By Line

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

Back to Overview