My good friend, Dr. Rob Miller introduced me to some of the ideas behind Agile programming as well as some of the practices. The whole idea behind Agile programming, it seems to me, is to embrace change and to focus development on important requirements. Nice to have things are put on a back burner.
There are significant differences between the requirements of programming and the requirements of instructional development. However, there appears to be commonality in what is driving me to look at Agile as a better way to do an instructional development.
When we discuss Agile ISD, we have to include the works of Vischer-Voerman, Gustafson and Plomp (1999). They advocate the inclusion of three additonal paradigms to the ADDIE process. These include a "communicative" (Customer Collaboration) paradigm which emphasizes consensus and communication among all stakeholders throughout the life-cycle of a project, and a "pragmatic" paradigm (Working Software?) that envisions repeated tryout and and making revisions based on stakeholder recommendations. They also support inclusion of an "artistic" paradigm that (I believe) gives developers more license to use their own and customer subjective criteria in creating the final project. The artistic paradigm meshes with the idea of Working Software and and Customer Collaboration portions of the Agile Manifesto.
Tuesday, April 1, 2008
Subscribe to:
Posts (Atom)
Posts
