Downloaded 18 times
Uploaded byTorranceLearning
Agile Project Management for Elearning – ATD TechKnowledge 2017
This document introduces the concept of Agile Project Management for instructional design. It advocates using Agile methods like iterative development, prioritizing work based on customer needs, and frequent collaboration to manage instructional design projects. The document outlines Agile concepts like writing learner personas and stories to define project scope, using story mapping and action mapping to plan work, and iterating through alpha, beta and final phases to catch errors early.
More Related Content
Similar to Agile Project Management for Elearning – ATD TechKnowledge 2017
More from TorranceLearning
Agile Project Management for Elearning – ATD TechKnowledge 2017
- 1. LLAMA Agile Project Managementfor Instructional Design Megan Torrance mtorrance@torrancelearning.com
- 2.
- 3. 3 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 6
- 7. How do youcurrently manage projects? 7
- 8. Our projects arecomplex & we have to keep up with an ever-increasing rate of change. 8
- 9.
- 10. The first dayof a project is the worst day to plan what the end product will be (and how much it will cost). 10
- 11. 11 Photo credit: ThinkStock115796521 Squirrel !
- 12. Every day youlearn something new about the project you're working on. 12
- 13.
- 14.
- 15. 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. 15
- 16.
- 17. 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. 17
- 18. The Agile Manifesto: Weare uncovering better ways of developing software by doing it and helping others do it... 18 source: www.agilemanifesto.org
- 19. We are uncoveringbetter ways of creating learning experiences by doing it and helping others do it. 19
- 20. Through this workwe have come to value: Individuals and interactions over processes and tools 20 source: www.agilemanifesto.org
- 21. Through this workwe have come to value: working software over comprehensive documentation 21 source: www.agilemanifesto.org
- 22. Through this workwe have come to value: customer collaboration over contract negotiation 22 source: www.agilemanifesto.org
- 23. Through this workwe have come to value: responding to change over following a plan 23 source: www.agilemanifesto.org
- 24.
- 25. Write learner personas Uselearner personas as a guide to keeping training design & your project focused. 25
- 26.
- 28. How do youchoose just one persona? • Quantity • Impact • Business Risk • Opportunity • Degree of Difficulty • Priority / timing for phases 28
- 29. Define scope withstories Write learner stories and story cards to define scope and plan the project. 29
- 30. Stories capture business needsand performance outcomes in a format that's useful for planning & production. 30 Story Cards 3 Things
- 31.
- 32. 32 As a I want soI can <who> <what> <why>
- 33. Use Agile story mapping forbuilding tools, things & software. 33
- 34. Use Cathy Moore's Action Mapping todefine stories for Agile learning projects. 34
- 35.
- 36. ! 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 Know . . .
- 38.
- 39.
- 40.
- 41. 41 Script: Megan Torrance.Illustrator: Serge Ratten
- 42. Plan the workvisibly Prioritize and schedule work 42
- 43. Define at the outsetwhat type of project this is. iStockphoto.com/4689051 43
- 44. 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. 44
- 45. Work iteratively until thework is ‘done’ Prioritize and schedule work 45
- 46. Make small mistakes faster. Skipthe big mistakes. Agile Explained, Menlo Innovations 46
- 47.
- 48.
- 49.
- 50. Do the simplestthing that could possibly work. 50
- 51.
- 52. Why iterate? 52 You always have somethingusable. You catch errors early. It’s easier to estimate. It’s psychologically way more satisfying.
- 53. How to iterate? 53 Alpha >Beta > Final By Project Phase By Delivery Medium By level of finish/functionality By language By audience
- 54. 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. 54
- 55.
- 56.