Download as PDF, PPTX
Uploaded byTorranceLearning
LSCon 2017 LLAMA: Agile Project Management for eLearning 101
The document discusses agile project management for eLearning, highlighting the iterative and incremental approach to design and implementation. It emphasizes maximizing customer value and team engagement, while advocating for practices like defining learner personas and using story mapping for project planning. Key principles from the Agile Manifesto are adapted for creating efficient learning experiences.
More Related Content
Similar to LSCon 2017 LLAMA: Agile Project Management for eLearning 101
More from TorranceLearning
LSCon 2017 LLAMA: Agile Project Management for eLearning 101
- 1. Session 108 LLAMA –Agile Project Management for eLearning Megan Torrance TorranceLearning Orlando, FL • March 22 – 24, 2017
- 2.
- 3. 4 You can buythis shirt on Amazon.com
- 4.
- 5. Think about your bestproject ever.
- 6. "Do more ofwhat works, & do less of what doesn't." Kent Beck, author of Extreme Programming (XP) Explained 7
- 7. Our projects arecomplex & we have to keep up with an ever-increasing rate of change. 9
- 8.
- 9. The first dayof a project is the worst day to plan what the end product will be (and how much it will cost). 11
- 10. 12 Photo credit: ThinkStock115796521 Squirrel!
- 11. Every day youlearn something new about the project you're working on. 13
- 12.
- 13.
- 14. Agile is … Aniterative, incremental method of guiding design & build projects in a highly flexible & interactive manner, focusing on maximizing customer value and fostering high team engagement. 16
- 15.
- 16. LLAMA is … Aniterative, incremental method of guiding instructional design & build projects in a highly flexible & interactive manner, focusing on maximizing customer value and fostering high team engagement. 18
- 17. THE AGILE MANIFESTO: Weare uncovering better ways of developing software by doing it and helping others do it... 19 source: www.agilemanifesto.org
- 18. We are uncoveringbetter ways of creating learning experiences by doing it and helping others do it. 20
- 19. Through this workwe have come to value: Individuals and interactions over processes and tools 21 source: www.agilemanifesto.org
- 20. Through this workwe have come to value: working software over comprehensive documentation 22 source: www.agilemanifesto.org
- 21. Through this workwe have come to value: customer collaboration over contract negotiation 23 source: www.agilemanifesto.org
- 22. Through this workwe have come to value: responding to change over following a plan 24 source: www.agilemanifesto.org
- 23.
- 24. WRITE LEARNER PERSONAS Use learnerpersonas as a guide to keeping training design & your project focused. 26
- 25.
- 26. How do youchoose just one persona? • Quantity • Impact • Business Risk • Opportunity • Degree of Difficulty • Priority / timing for phases 29
- 27. DEFINE SCOPE WITH STORIES Writelearner stories and story cards to define scope and plan the project. 30
- 28. Stories capture business needsand performance outcomes in a format that's useful for planning & production. 31 Story Cards 3 Things
- 29.
- 30. 33 As a I want soI can <who> <what> <why>
- 31. Use Agile story mappingfor building tools, things & software. 34
- 32. Use Cathy Moore's Action Mappingto define stories for Agile learning projects. 35
- 33.
- 34. ! Design a solutionto meet stated needs ! Remove a kidney stone ! Provide verbal feedback to teammates ! Collect & enter data accurately ! Nail roof shingles safely Practice in Training Business Goal that solves a Business Problem Adapted from: Cathy Moore Know . . .
- 35. PLAN THE WORK VISIBLY Prioritizeand schedule work 43
- 36. Define at the outsetwhat type of project this is. iStockphoto.com/4689051 44
- 37. Zero-Surprises Project Management 1. Breakbig things into little ones. 2. Plan from the big to the little. 3. Work from the little to the big. (if they don’t match, start talking) 4. Make it visual. 45
- 38. 46 Bottom-up Planning is basedon estimates
- 39. 47 Top-Down Planning: SME &Reviewer schedules Holidays Resource Plans Hard part
- 40.
- 41.
- 42.
- 43.
- 44.
- 45. WORK ITERATIVELY until thework is ‘done’ Prioritize and schedule work 53
- 46. Make small mistakes faster. Skipthe big mistakes. Agile Explained, Menlo Innovations 54
- 47.
- 48.
- 49.
- 50. Why iterate? 60 You always havesomething usable. You catch errors early. It’s easier to estimate. It’s psychologically way more satisfying.
- 51. How to iterate? 61 Alpha >Beta > Final By Project Phase By Delivery Medium By level of finish/functionality By language By audience
- 52. Megan’s Rules for Iterations Itdoes real work. Someone else has to use it. You gather data. Data informs the work to do in the next iteration. 62
- 53.
- 54.