130 likes | 286 Views
Situated Innovation. Yvonne Dittrich Department of Software Engineering and Computer Science Sara Eriksén Department of Human Work Science, Media Technique and Humanities. ?. Innovation Systems. Knowledge Transfer. Triple Helix. Diffusion. ?. ?. Three Cases.
E N D
Situated Innovation Yvonne DittrichDepartment of Software Engineering and Computer Science Sara EriksénDepartment of Human Work Science, Media Technique and Humanities
? Innovation Systems Knowledge Transfer Triple Helix Diffusion ? ?
Three Cases • Design of IT in Use – supportive technologies for public services • April 00 – Dec. 02, financed by Vinnova • participants: BTH, 5 municipalities, 2 software providers, 1 call center • Design of Database Applications in Use • Jan. 00 – Dec. 01, financed by The Knowledge Foundation • participants: BTH, Europolitan/Vodafone, DieData • e-government Arena • July 02 – Dec 03, financed by the European Commission • participants: BTH, 3 municipalities, 2 software providers
Situated Innovation • occures through specific configurations of • designers and developers • users • and sometimes also researchers • takes place in and contributes to different dimensions • improves the practices of developing and deploying software • scientific insight
Why ICT? • ICT is highly malleable • design tends to invade use • use-related qualities are highly situational • ICT research has to take this into account Empirical research in close interaction with practice is an important resource for applied ICT.
Case 1: Design of IT in Use • public service provision in one-stop shops • on-going development of ICT in use • long term provider - customer relationship • Participatory Design in practice
Broadening the Scope of Situated Innovation • ’seeing differently’ • reflective and mirroring role of the researchers • from participatory design to participatory research Cultivating spaces for situated innovation
Case 2: Design for Design in Use • developing flexible systems that can be easily adapted to changes in the business • established co-operation between in-house software developers and business units • interaction of use contexts, development practices and technical infrastructure • ’artful integration’ instead of ’design from nowhere’
Achieving Transferability • understanding software development practices • co-operating around method development • evaluating the deployment of the methods • -> improved understanding of the applicability of methods in situ Co-operative Method Development
Case 3: An arena for e-Government • regional joint venture • short term projects in the context of a long-term research and development co-operation • multi- and interdisciplinary co-operation between telecommunication, software engineering, economics and human work science • integrating e-services, e-democracy and e-governance
Mutual Accountability • making use of multi-perspectivity both in research and in practice • making short term projects and long term research interests work together • co-ordinating rythms and rationales • flexibility of researchers and practitioners • mutual understanding and respect • making goals and ambitions visible
Summing up • researchers contribute with an outside perspective, methodological and technological knowledge … … and provide spaces for reflection on action which enhances reflection in action • practitioners’ requirements, constraints and possibilities challenge scientific knowledge … through which a deeper understanding of ICT development and deployment is developed. • to accommodate the different rationales the different rythms have to be accomodated in the co-operation as well
Situated Innovation • seeing innovation systems from within • moving from studying dynamics to taking action in the ’triple helix’ • research changes when it becomes involved in practices it is meant to contribute to • retaining continuity and independence is necessary to broaden the space and scope of innovation