OCTOBER 25 TO 29, 2009
Dr. Orit Hazzan is an associate professor at the Department of Education in Technology and Science of the Technion, Israel. In May 2004 she published her book Human Aspects of Software Engineering, co-authored with the late Jim Tomayko. Her second book - Agile Software Engineering - co-authored with Yael Dubinsky, was published by Springer in 2008. In parallel to her research work, she is a consultant for several software projects in the Israeli software industry. She presents her research at computer science and software engineering education conferences, as well as at conferences on software engineering and agile software development.
Dr. Yael Dubinsky is affiliated with the Software and Services group in IBM Haifa Research Lab. She is a visiting member of the human-computer interaction research group at the Department of Computer and Systems Science at La Sapienza, Rome, and for more than ten years the instructor of project-based courses in the Computer Science Department at Technion, Israel. Her research interests involve aspects in software engineering and information systems. Yael has a significant experience with guiding agile implementation processes in the industry and academia. Her book on Agile Software Engineering, co-authored with Orit Hazzan, was published by Springer in 2008.
In this workshop we focus on the notions of reflection and retrospective and their impact on the development process. Reflection usually refers to the individual's thinking about what he or she has accomplished; retrospective is usually conducted in teams, and is partially based on the individuals' reflections performed during the retrospective sessions. Both activities are based on the reflective practitioner perspective introduced by Schön in his two books The Reflective Practitioner in 1983 and Educating the Reflective Practitioner in 1987. The reflective practitioner perspective guides professional practitioners (such as architects, managers, musicians and others) towards examining and rethinking their professional creations during and after the accomplishment of the process of creation.
The working assumption of the reflective practitioner perspective is twofold. First, the reflection practice provides a learning mechanism thus improves team members' proficiency and performance. Second, retrospective sessions provide a periodically examination of the development process, hence involves reflection on issues related to team goals, decision making, and follow up on previous decisions. In the workshop we examine different models of reflections and retrospectives in software development teams, outcomes of such processes, and relationships among the team and the individuals in such processes.