Agile isd by_lisa_cooney
- 1. Agile Instructional Systems Design (Agile ISD) OCTOBER 5, 2016 LISA COONEY
- 2. About Me • Have a Masters in ISD • Am an on-site Government contractor • Am not selling anything • Lead a very small Agile ISD team https://www.linkedin.com/in/lisacooney
- 3. My Agile Story • Learned Agile while building a course on it • Have been using Agile ISD successfully for 3 years • Collected various Agile certifications • Have started a book on Agile ISD (need to get going on that …..)
- 4. What I did • Developed a two-week course • Course was overwhelmingly successful • Presented at *I/ITSEC Conference in 2015 * Interservice/Industry Training, Simulation, and Education
- 5. What I do now • Manage a curriculum of six courses • Use Agile management online collaboration tools • Participate in Agile Meetups, conferences, etc. • Talk about Agile all the time
- 7. Waterfall Waterfall Software Development Process ADDIE* * Analysis, Design, Development, Implementation, Evaluation Requirements Design Implementation Verification (Testing) Operations & Maintenance Analysis Design Development Implementation Evaluation
- 9. Iterative Software Development Initial Planning Planning Requirements Analysis and Design Deployment Implementation Testing Evaluation
- 10. Addie - Sequential Design Document Agile ISD - Iterative Portrait of a woman outdoors ADDIE versus Agile Design Document
- 12. The Business Case for Agile Value Risk ROI ROI/Value ROI/Value Time Waterfall Agile © Grant Thornton LLP. All rights reserved.
- 13. Triple Constraint Iron Triangle FIXED FLEXIBLE Content ContentTime Cost ADDIE AGILE ISD Time Cost
- 14. All possible content for the course Highest Priority Content New Content that emerges after development starts Content that makes it into the course Content
- 15. Kanban To Do In Progress Done
- 16. Kanban for ISD To Do (Backlog) In Progress Done Write Lesson 4 Write outlines for Module 6 Implement Feedback from Pilot B into Course 1 Write lesson 5 (Alice) Adjust Course 3 for new Blackboard features (Joe) Prepare for Course 2 Pilot B (Keisha) Write lesson 3 QA Modules 1-4 Course 1
- 17. No Kidding Kanban for ISD To Do This Sprint In Progress In SME Review In ISD Review In Client Review Done
- 18. Lesson or Task Acceptance Criteria • • • • Due date:Being worked by: Story PointsPriority Story Points = Estimate of Level of Effort Priority is set by the Client Team Members choose tasks Due Date is helpful for recurring or routine tasks Acceptance criteria define Done – they are conditions that must be met
- 19. Examples Update Module 1 Lesson 3 Acceptance Criteria • SME input has been obtained and adjudicated • ISD has run through the Finalization Checklist • Graphics have been updated • Client has approved the lesson Due date:Being worked by: Lisa Story Points 2 Priority High
- 20. Examples Revise Test Items Module 4 Lesson 2 Acceptance Criteria • Test item analysis has been completed • Faulty test items have been identified • SME has re-written bad test items • ISD has checked test items • Client has approved test items Due date: 11/4 Being worked by: Lisa Story Points 1 Priority High
- 21. Early and Frequent Releases MeetingTrainingNeed Time Waterfall Single Release Agile ISD Frequent Releases Useful Training Delivered
- 22. Release Planning
- 23. Scrum
- 24. Scrum Products and Traditional Equivalent Product Backlog Overall project task list Sprint Backlog To-do list for a short interval Product Increment Short-term, mid-project deliverable
- 25. Scrum Meetings and Traditional Equivalent Sprint Review Sprint Planning Backlog Grooming Sprint Retrospective Daily Scrum Feedback Session Planning Meeting Outlining and Defining the Work Lessons Learned Daily Stand-up • What did I do yesterday? • What will I do today? • What are my impediments?
- 26. Scrum Roles and Traditional Equivalent Product Owner Scrum Master Development Team Stakeholders Client/Customer Team Lead Team Members Stakeholders
- 27. Agile Values and Principles
- 28. Agile Values We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 29. Agile Principles 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software courseware. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working software courseware frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
- 30. Agile Principles 4. Business people and developers must work together daily throughout the project. 5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
- 31. Agile Principles 7. Working software courseware is the primary measure of progress. 8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9. Continuous attention to technical excellence and good design enhances agility.
- 32. Agile Principles 10. Simplicity--the art of maximizing the amount of work not done--is essential. 11. The best architectures, requirements, and designs emerge from self-organizing teams. 12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
- 33. Why Agile Works • Makes client happy when value is delivered earlier • Reveals risks early when they can be mitigated • Improves product quality
- 34. Why Agile Works Agile taps into innate human need to: • Be in control of our own work • Work collaboratively towards a common goal • Take pride in our work (sprint review) • Know what is going on (transparency) • Solve problems as a team • Work at a sustainable pace • Have fun!
- 38. How do you get to Carnegie Hall? Practice, practice, practice
- 39. Agile ISD Take Aways • Agile is the wave of the future for ISD • Kanban is a good way to get started • Once you learn it, you will love it!
- 40. Agile ISD Links Implementation of Agile Methods within Instructional Systems Design: A Case Study (by Dr. Anne Little and Lisa Cooney) Agile Curriculum Design Model (by Marian Weilleke) LLAMA (A Lot Like Agile Management Approach) by Megan Torrance By Megan Torrance, from Learning Solutions Magazine: What Does it Mean to be Agile? Reconciling ADDIE and Agile The Successive Approximation Model (SAM) from Allen Interactions The Scrum Guide (by Jeff Sutherland) The Scrum Reference Card (by Michael James) The Agile Alliance on Scrum