The Agile ADDIE Framework was developed to overcome challenges such as a constantly changing domain, external threats to the development process, and the need for expedited timelines while still creating quality products. Using agile theory, including the agile manifesto, as a theoretical framework, the Agile ADDIE Framework was created. The Agile ADDIE Framework implements agile elements into the traditional ADDIE model, such as an iterate, assess, and align (IAA) cycle in an effort to increases in flexibility, quality, and efficiency.
A mixed method action research project reviewed the impact that agile elements had on the ADDIE model at the National Simulation Center. The working group participants underwent biweekly meetings using scrum methodology. Data collection included pre- and post-intervention interviews, weekly structured reflections, focus groups that occurred throughout the development process, and a burndown log to track performance. Additionally, the course that was created using the Agile ADDIE Framework was compared to a product that was completed using the traditional ADDIE model by a panel of instructional designers.
Participants identified that the Agile ADDIE Framework was able to create a higher-quality product in a shorter amount of time when compared to a training support package developed using the traditional ADDIE model. Several themes emerged from the data, including the Agile ADDIE Framework was perceived to be more flexible and engaging to subject matter experts. There was also a discussion involving lesson learned, limitations, and implications for both practice and the domains. Future research considerations include the implementation of the Agile ADDIE Framework in a more generalized study. This study presents a framework that enables traditional ADDIE model instructional design operations into an agile era.
This paper will demonstrate that the Agile development process helps to ensure incremental work on an Unreal Engine game project is achieved by presenting a product produced in Unreal Engine along with my experience in utilizing Scrum to facilitate the game’s development. Section 2 discusses project goals and motivations for using Agile, using Unreal Engine, and for the choice of genre in the final product. Section 3 contextualizes these goals by presenting the history of Unreal Engine, the novel applications of Unreal Engine, and the use of Unreal Engine in the development of Heady Stuff. Section 4 presents findings from the project’s development by describing my use of Agile and by presenting the steps taken in learning Unreal Engine. Section 4 continues by highlighting important development considerations in the use of Blueprints, C++, and HLSL in Unreal Engine. The section ends with the presentation of project feedback, its incorporation in the final product, and the resources used to assist development. Section 5 compares the workflow, help resources, and applications of Unreal Engine with those of Unity, another highly popular game engine. Lastly, Section 6 performs a post-mortem on the overall development process by considering how well Agile development processes were upheld along with how much of the original plans in the Design Document was present in the final product. Additionally, the section presents the major challenges encountered during project development. These challenges will help in proposing possible best practices for game development in Unreal Engine.
