Delivering Learning and Development solutions that meet organizational needs requires a strategic approach. Choosing the right methodology is a crucial factor in success. The ADDIE methodology has been the predominant choice for instructional design for over 40 years. Invented in an era of instructor-led, classroom learning, the ADDIE methodology has lost popularity with the rise of eLearning.
As learning designers look to respond more quickly to the training needs of the business, many are turning their attention to the potential of working under an Agile instructional design methodology. Both ADDIE and Agile methodologies involve Analysis, Design, Development, Implementation, and Evaluation as part of their process, but the flexibility of the Agile methodology sets it apart. Following is a review of each process and its benefits.
ADDIE
As a linear, waterfall model, ADDIE is easy to understand and use. Each phase in this proven method has specific deliverables and a review process. Phases are completed one at a time and do not overlap. Design does not begin before analysis is finished. This means errors can only be fixed during the active phase. While this process may work well for small projects where requirements are well-defined, it is not desirable for complex projects where requirements change frequently. If your target audience has fixed or fairly consistent needs, a non-iterative approach is likely suitable. Completion times are easier to gauge with ADDIE, as larger pieces of the project are planned in advance. Additionally, project management can be easier with ADDIE as it is based on a comprehensive master plan.
AGILE
Formally launched in 2001, the Agile methodology is an acronym for Align, Get set, Iterate and implement, Leverage and Evaluate. The idea behind Agile is to create a more “agile,” nimble, flexible and adaptable design process. Agile incorporates the same phases of ADDIE, but completes them in a different order and tempo. Based on the philosophies set forth in the Agile Manifesto, the steps for Agile instructional design are the following:
Plan – Instructional designers meet with all stakeholders, teammates and users to brainstorm and formulate a plan for the development of the eLearning course.
Content – All members of the group agree upon the core eLearning content of the eLearning course and break it into segments.
Rapid development – The segment of the eLearning content that was discussed is then developed rapidly.
Review – Address any modifications or additions that need to be made before moving forward.
Iteration – Once all the issues have been remedied and concerns have been discussed, the eLearning team then repeats the process again for each section of the eLearning course. Thus, every segment of the eLearning content is fully developed prior to creating the next module or unit.
As organizations continue to seek faster and more efficient ways to train their employees, it is often necessary to use an iterative process that gives them the opportunity to use collaboration, feedback and iterations to streamline the eLearning design and development process. Instead of focusing on quality only in the Evaluation phase of ADDIE, quality is inspected throughout the process giving more opportunity to correct errors. This in turn provides a greater degree of transparency to stakeholders to reaffirm a mutual understanding of the project’s direction by the stakeholders and e-learning team.
Agile methodologies like Scrum or Lean were created specifically for software development. To address the nuances of the learning design process, some organizations use hybrid approaches that incorporate both the structured and flexible aspects of ADDIE and Agile. The SAM (Successive Approximation Model) and LLAMA (Lot Like Agile Management Approach) methodologies provide an Agile version of ADDIE to increase speed to market and quality of the end product.
While the Agile methodology allows eLearning teams to flex to dynamic and ever-changing business requirements, the Agile methodology is not without its drawbacks. Agile projects do not support a fixed cost model. As business requirements evolve throughout the lifecycle of an Agile project, there may be unpredicted expenses and modifications. Frequent deliverables and the need to get each work product approved is demanding and time-consuming, requiring the availability of stakeholders, subject matter experts and the end users. Frequent delivery also puts a lot of pressure on e-learning teams to deliver high quality deliverables within a very short period. Lastly, the heavy stakeholder participation of Agile projects can run the risk of stalling the project.
In order to determine whether ADDIE, Agile or a hybrid approach are best for your project, consider how effective it will be relative to the size of the project, project timelines, and the type of content. Although ADDIE is more traditional while Agile works well in today’s fast-paced working environments, both methods share a common base and are highly valued and widely applied. If you would like more information on which approach best matches your business need, contact VisionCor today and let our Learning & Development consultants set your next project up for success.
