Challenge to Learn

article thumbnail

Agile eLearning development (6): Recap

Challenge to Learn

Over the past weeks I have written a series of blog post on agile eLearning development. A must read for anyone involved in eLearning development. A contribution by Ken Taggert who is developing an educational app for kids. There is much more to tell, but I decided that it is enough for now. Leaving ADDIE for SAM.

Agile 193
article thumbnail

Agile eLearning development (2): Culture

Challenge to Learn

I planned to write this second post on agile eLearning development about the backlog and estimations. This is the third post in a series on agile eLearning development: Post 1: Review on Michael Allen’s book ‘Leaving ADDIE for SAM. Post 2: Agile eLearning development: business goals and road map.

Agile 221
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Agile eLearning development (4): Planning and execution

Challenge to Learn

This method of planning and execution can be used for eLearning development without any changes and I promise you it will be a huge difference. This post is part of a series on agile eLearning development: Review on Michael Allen’s book ‘Leaving ADDIE for SAM. Agile eLearning development (2): Culture.

Agile 205
article thumbnail

Agile eLearning development: business goals and road map

Challenge to Learn

This is a first post in a series of post on Agile eLearning development. I do believe that agile software development can offer us even more very practical ‘best practices’ that we can apply to eLearning. Before I can do that I have to introduce the roles in this process and map them to ‘e-Learning development roles’.

Agile 242
article thumbnail

Agile eLearning development (3): Best practices, Demo’s, user stories and backlog

Challenge to Learn

In the previous post on agile eLearning development I wrote about culture. Agile development offers a range of best practices that are relatively easy to implement. Agile development works in short sprints (one or 2 weeks). Post 2: Agile eLearning development: business goals and road map. But there is hope.

Agile 208
article thumbnail

Agile tips that will improve your eLearning development

Challenge to Learn

You can apply the lessons learned from agile software development to eLearning development as well. This post contains some simple tips that you can apply to eLearning development. It allows us to deliver a new version each week, be in sink with our road map and with our customers. Make sure you have a client.

Agile 100
article thumbnail

Book review: Leaving ADDIE for SAM: will agile eLearning development become mainstream?

Challenge to Learn

It is clear that both authors have a few decades of combined experience in eLearning development. This enables them not only to develop an approach but explain it with very practical examples. And finally some links to earlier post I wrote on agile eLearning development: A post with links to other ‘agile’ eLearning posts.