Using iterative development (and Agile) for better project management
•Download as PPTX, PDF•
0 likes•600 views
eLearning Guild Project Management Spotlight session delivered July 20, 2016
Recommended
More Related Content
Similar to Using iterative development (and Agile) for better project management
Similar to Using iterative development (and Agile) for better project management (20)
More from TorranceLearning
More from TorranceLearning (20)
Recently uploaded
Recently uploaded (20)
Using iterative development (and Agile) for better project management
- 1. https://commons.wikimedia.org/wiki/File:Apollo_15_flag,_rover,_LM,_Irwin.jpghttps://commons.wikimedia.org/wiki/File:Apollo_15_flag,_rover,_LM,_Irwin.jpg Using Iterative Development for Better Project Management
- 2. https://commons.wikimedia.org/wiki/File:Apollo_15_flag,_rover,_LM,_Irwin.jpg How To Land On the Moon in 8 Easy Steps
- 4. 4
- 5. 5 How iterative is your development work? We run in full-on Agile, SAM, or rapid prototyping style development. We’re experimenting. We do a standard alpha beta gold approach Iterative development would never fly around here. It’s got to be perfect or it will never see the light of day.
- 6. https://commons.wikimedia.org/wiki/File:Apollo_15_flag,_rover,_LM,_Irwin.jpg Example source: Tom Ayerst Let’s go to the moon! 1. Build a rocket engine that has enough thrust. 2. Build a rocket that can lob a man into space. 3. Build one that can lob him into orbit. 4. Dock two space vehicles in orbit. 5. Land an unmanned one-way vehicle on the moon to check the environment. 6. Fly round the moon. 7. Test out the lander near the moon. 8. Land on the moon.
- 7. 1. SAM & Rapid prototyping are iterative approaches. 2. Agile & LLAMA are project management approaches designed for iterative development. 3. You may already be doing it, but calling it something different. 4. It’s not unique to L&D projects. things you need to know about iterative development And #3 will blow your mind.
- 8. 8 Let’s play a game
- 12. “The need to predict the future is great. Our ability to do so is minimal.” Richard Sheridan 12
- 14. 14 A D I/E D I/E D DD D Iteration 1 Iteration 2 Iteration 3 TIME
- 15. Why iterate? 15 You always have something usable. You catch errors early. You don’t get too far off track. It’s easier to estimate. It’s psychologically way more satisfying.
- 16. 16
- 17. 17
- 18. Do the simplest thing that could possibly work. 18
- 20. How to iterate? 20 Alpha > Beta > Final By Project Phase By Delivery Medium By level of finish By depth of functionality By language By audience
- 21. 21
- 22. Megan’s Rules for Iterations 1. It does real work. 2. Someone else has to use it. 3. You gather data. 4. You use the data to decide what work to do in the next round. 22
- 23. Where’s the data? 23 Level 1 evaluations (satisfaction) Level 2 evaluations (test scores) Level 3 assessment (performance) Interviews Observations xAPI
- 25. A D I/E D I/E D DD D TIME When is “done”?
- 27. Vitamin Angels eVAS+D for Providers
- 28. ZingTrain’s Guide to Giving Great Service
Editor's Notes
- Introduce Megan
- So what is iterative development? It’s a process of getting closer and closer to your goals … instead of running right out and doing it. Why on earth would you take this seemingly slow and painful route?
- IBM DeveloperWorks This leads us to adopt a style of software development where the assertions inherent in the plan are repeatedly challenged and evaluated by the design and development of demonstrable versions of the system, each of which is objectively shown to reduce the project risk and build upon the other to form the finished solution. This style of development is more commonly known as iterative and incremental development, which we define as: A style of development that involves the iterative application of a set of activities to evaluate a set of assertions, resolve a set of risks, accomplish a set of development objectives, and incrementally produce and refine an effective solution. It is iterative in that it involves the successive refinement of the understanding of the problem, the solution's definition, and the solution's implementation by the repetitive application of the core development activities.2 It is incremental in that each pass through the iterative cycle grows the understanding of the problem and the capability offered by the solution. Several or more applications of the iterative cycle are sequentially arranged to compose a project.
- But what happens when change happens AFTER it’s supposed to?
- You always have a running version of the program, eg, if you run out of time, you can deliver the last iteration, which may not have all functionality, but it does something. This is usually worth more to your instructor than a program which doesn't even compile yet. It helps identify the source of the last error (compilation or execution), because you know it's in the code you just added in this iteration. This makes finding bugs much faster. It's psychologically more satisfying to get positive feedback on your work, ie, a running program. Corrections early in development generally take less time than later in the development process.
- http://objectivesoftwaresolutions.com/content/iterative-development-model txweb-design.com http://www.dcon.com.br/jd.comment/articles/notes-java/15principles_and_practices/iterative/30Interative-incremental-dev.html http://jasonunes.blogspot.com/2008_04_01_archive.html http://www.abreit.com.au/Services/SoftwareDevelopment
- You always have a running version of the program, eg, if you run out of time, you can deliver the last iteration, which may not have all functionality, but it does something. This is usually worth more to your instructor than a program which doesn't even compile yet. It helps identify the source of the last error (compilation or execution), because you know it's in the code you just added in this iteration. This makes finding bugs much faster. It's psychologically more satisfying to get positive feedback on your work, ie, a running program. Corrections early in development generally take less time than later in the development process.
- Who defines when it’s done?
- Team members include: Instructional Designers Developers Stakeholders Agile Coach or Project Manager Learners Subject Matter Experts Who else?
- Key takeaways