Challenge to Learn
MAY 29, 2013
I planned to write this second post on agile eLearning development about the backlog and estimations. How does this apply to eLearning? The developers will commit to these user stories and build them in short sprints (periods of one or two weeks) and then they will demo them. Post 3: Agile eLearning development (2): Culture.
Challenge to Learn
JUNE 25, 2013
User stories will only be presented at demo when they are done. Done means that you could decide to put them in the production version of the product straight after the demo. 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 site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Challenge to Learn
JUNE 4, 2013
In the previous post on agile eLearning development I wrote about culture. After every sprint there is a demo where the development team shows the result of the work of the past sprint. The product owner will check during the demo if the solutions build match the requirements from the user stories and will accept them (or not).
Challenge to Learn
JUNE 25, 2015
Do you have questions in general about eLearning? Please note that I will not do a full demo, if you want that please watch our demo video. Please note that I will not do a full demo, if you want that please watch our demo video. And finally I love to talk about eLearning so try me out.
Challenge to Learn
FEBRUARY 23, 2016
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. If you create eLearning for your own organization it has to be an internal client. Work in short sprints and demo your work!
Challenge to Learn
MARCH 19, 2013
The last 2,5 years my focus has been on eLearning authoring and I think this a very informative post on selecting a LMS. As you are searching for your perfect Learning Management System (LMS), you need to have a sense of any problems in your organization to make sure you get the right prescription for an eLearning solution.
Challenge to Learn
FEBRUARY 6, 2015
You do a demo every week or every two weeks, showing them what you have done so far and you will get feedback on what you have created. After a demo you will decide together what the next priorities are (see point 3). At the end of each sprint the development team does the demo. Create an agile culture.
Expert insights. Personalized for you.
221 
Let's personalize your content