LSCon 2017 LLAMA: Agile Project Management for eLearning 101
•
0 likes•426 views
How do you keep your project from falling short in delivering client (internal or external) needs on time, and within budget? I'll show you how!
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to LSCon 2017 LLAMA: Agile Project Management for eLearning 101
Similar to LSCon 2017 LLAMA: Agile Project Management for eLearning 101 (20)
More from TorranceLearning
More from TorranceLearning (20)
Recently uploaded
Recently uploaded (13)
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
- 3. 4 You can buy this shirt on Amazon.com
- 4. 5
- 5. Think about your best project ever.
- 6. "Do more of what works, & do less of what doesn't." Kent Beck, author of Extreme Programming (XP) Explained 7
- 7. Our projects are complex & we have to keep up with an ever-increasing rate of change. 9
- 9. The first day of 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: ThinkStock 115796521 Squirrel!
- 11. Every day you learn something new about the project you're working on. 13
- 14. Agile is … An iterative, 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. 17
- 16. LLAMA is … An iterative, 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: We are uncovering better ways of developing software by doing it and helping others do it... 19 source: www.agilemanifesto.org
- 18. We are uncovering better ways of creating learning experiences by doing it and helping others do it. 20
- 19. Through this work we have come to value: Individuals and interactions over processes and tools 21 source: www.agilemanifesto.org
- 20. Through this work we have come to value: working software over comprehensive documentation 22 source: www.agilemanifesto.org
- 21. Through this work we have come to value: customer collaboration over contract negotiation 23 source: www.agilemanifesto.org
- 22. Through this work we have come to value: responding to change over following a plan 24 source: www.agilemanifesto.org
- 24. WRITE LEARNER PERSONAS Use learner personas as a guide to keeping training design & your project focused. 26
- 26. How do you choose just one persona? • Quantity • Impact • Business Risk • Opportunity • Degree of Difficulty • Priority / timing for phases 29
- 27. DEFINE SCOPE WITH STORIES Write learner stories and story cards to define scope and plan the project. 30
- 28. Stories capture business needs and performance outcomes in a format that's useful for planning & production. 31 Story Cards 3 Things
- 29. 32
- 30. 33 As a I want so I can <who> <what> <why>
- 31. Use Agile story mapping for building tools, things & software. 34
- 32. Use Cathy Moore's Action Mapping to define stories for Agile learning projects. 35
- 34. ! Design a solution to 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 Prioritize and schedule work 43
- 36. Define at the outset what type of project this is. iStockphoto.com/4689051 44
- 37. Zero-Surprises Project Management 1. Break big 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 based on estimates
- 39. 47 Top-Down Planning: SME & Reviewer schedules Holidays Resource Plans Hard part
- 40. 48
- 41. 49
- 42. 50
- 43. 51
- 44. 52
- 45. WORK ITERATIVELY until the work is ‘done’ Prioritize and schedule work 53
- 46. Make small mistakes faster. Skip the big mistakes. Agile Explained, Menlo Innovations 54
- 47. 55
- 50. Why iterate? 60 You always have something 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 It does real work. Someone else has to use it. You gather data. Data informs the work to do in the next iteration. 62
- 53. 63