DevLearn 2014 - Ten Things eLearning Developers Can Learn from Software Developers

Modern eLearning courses are technology solutions developed and implemented using many of the same techniques and tools that software developers use. Both share similar challenges: subject matter experts to navigate, aggressive deadlines to manage, assorted files and assets to organize, and an integrated approach to delivery, accounting for various hosting and browsing systems plus ongoing user support.

In this session you will examine the common evolution of eLearning and software development. Specifically you will explore techniques, agile processes, and best practices from the software development world that can be directly applied to your work. You will leave this session able to streamline your eLearning development and strengthen the quality of the solutions you produce.

In this session, you will learn:

Tools for managing project communication, assets, and schedules
Techniques for satisfying stakeholders
Agile development and delivery practices that can be applied immediately
Quality control practices to support robust delivery

Transcript

1. DevLearn 2014 Ten Things eLearning Developers Can Learn from Software Developers PRESENTED BY JASON RIMMER, SOFTWARE TYPE PERSON RIMMER CREATIVE GROUP Copyright 2014. Rimmer Creative Group, LLC. All Rights Reserved.
2. eLearning is a Technology Solution. “ ” - Trina Rimmer
3. Technology … §  CODE §  DEFECTS §  PLATFORMS §  TOOLS …Solution §  STAKEHOLDERS §  SUBJECT MATTER EXPERTS §  SCHEDULES
4. EVOLVE YOUR PROCESS ALONGSIDE CAPABILTIES Evolution of Man by RedJackOfClubs, http://j.mp/10D6mtQ
5. 1 )  ESTABLISH PROJECT GROUND RULES 2 )  TRACK EVERYTHING
6. 3 )  FLEX YOUR PROCESS
7. PASS THE PENNIES DELIVER MORE BY DOING LESS
8. THE CHALLENGE The customer wants 20 pennies turned over 3 times. Given a production line How can this be done as fast as possible? Modeling a project with Elaboration, Construction, and Verification phases.
9. TURN ALL & PASS
10. HOW DID THEY DO? Entire effort took 53 seconds. OBSERVATIONS Customer waited a long time Workers were idle (paid hourly?) OTHER OBSERVATIONS?
11. TURN 5 & PASS
12. HOW DID THEY DO? Entire effort took 38 seconds. (35% reduction) OBSERVATIONS Customer saw results early (in 17 seconds) Workers less idle OTHER OBSERVATIONS?
13. OPTIMIZATIONS Batch size of two: 27 seconds & output in 7 seconds (worker suggested improvement) IS ONE THE ANSWER? 46 seconds, output in 5 seconds BETTER WITH PRACTICE? Batch size of twenty: 54 seconds
14. 5 )  USE THE RIGHT TOOL 4 )  SAVE YOUR HISTORY
15. 6 )  OPTIMIZE TIME TO VALUE
16. 7 )  FOCUS ON THE MVP Minimally Viable Product
17. 8 )  MAKE TESTING REPEATABLE 9 )  KEEP STAKEHOLDERS ON THE TEAM Plan   Test   Test   Review   Results   Correct  
18. 10 )  BOUNDING FOR THE WIN ACT EVALUATE MOVE
19. TO HELP TOOLS EXECUTION MANAGEMENT §  Blossom, https://www.blossom.io/ §  Trello, https://trello.com/ §  Asana, https://asana.com/ §  Flow, http://www.getflow.com/ §  Dropbox, https://www.dropbox.com/ §  GitHub, https://www.dropbox.com/ §  BitBucket, https://bitbucket.org/ CHANGE CONTROL
20. TO HELP MORE TOOLS ISSUE TRACKING §  Jira, https://www.atlassian.com/software/jira §  Lighthouse, https://lighthouseapp.com/ §  Github, Bitbucket, Trello, Blossom, ... §  Slack, https://slack.com/ §  HipChat, https://www.hipchat.com/ §  Kanban, http://en.wikipedia.org/wiki/Kanban_(development) §  Agile Development, http://en.wikipedia.org/wiki/Agile_software_development COMMUNICATION METHODOLOGIES
21. THANKS! jason@rimmer.net jasonrimmer.com @jrimmer jasonrimmer.com/events/devlearn2014