The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.04 - July/August (2011 vol.28)
pp: 74-83
ABSTRACT
Both the software industry and academia promote collaboration to solve challenges together that neither can solve alone. Collaboration brings opportunities to understand and improve in ways not possible when working apart, but it succeeds only if both parties are contributing. A collaboration model developed from eight years' experience setting up and managing a research center explicitly focused on industry needs is based on five success factors enabling research results (need orientation, industry goal alignment, deployment impact, industry benefit, and innovativeness), five success factors enabling research activities (management engagement, network access, collaborator match, communication ability, and continuity), and 10 action principles for industry-academia collaboration management.
INDEX TERMS
software prototyping, groupware, software engineering, software management, continuity, agile collaborative research, industry-academia collaboration, software industry, research center, management engagement, network access, collaborator match, communication ability, Collaboration, Management, Product development, Business, Adaptation model, Modeling, Training, industry–academia collaboration, research and development management, collaborative practice research
CITATION
"Agile Collaborative Research: Action Principles for Industry-Academia Collaboration", IEEE Software, vol.28, no. 4, pp. 74-83, July/August 2011, doi:10.1109/MS.2011.49
REFERENCES
1. D.H. Rombach, and R.E. Achatz, "Research Collaboration between Academia and Industry," Proc. Future of Software Eng. (FOSE 07), IEEE CS Press, 2007, pp. 29–36.
2. M. Beer, "Why Management Research Findings Are Unimplementable: An Action Science Perspective," Reflections, vol. 2, no. 3, 2001, pp. 58–65.
3. L. Mathiassen, "Collaborative Practice Research," Information, Technology & People, vol. 14, no. 4, 2002, pp. 321–345.
4. D.A. Schön, The Reflective Practitioner: How Professionals Think in Action, Basic Books, 1983.
5. L.M. Applegate, "Rigor and Relevance in MIS Research," MIS Quarterly, vol. 23, no. 1, 1999, pp. 1–2.
6. T. Barnes, I. Pashby, and A. Gibbons, "Effective University-Industry Interaction: A Multi-case Evaluation of Collaborative R&D Projects," European Management J., vol. 20, no. 3, 2002, pp. 272–285.
7. E.M. Mora-Valentin, A. Montoro-Sanchez, and L.A. Guerras-Martin, "Determining Factors in the Success of R&D Cooperative Agreements between Firms and Research Organizations," Research Policy vol. 33, no. 1, 2004, pp. 17–40.
8. A. Börjesson, Making Software Process Improvement Happen, doctoral dissertation, IT Univ.of Götenburg, 2006.
9. L. Pareto, P. Eriksson, and S. Ehnebom, "Concern Visibility in Base Station Development: An Empirical Investigation," Proc. 12th Int'l Conf. Model-Driven Eng. Languages and Systems (Models 09), LNCS 5795, Springer, 2009, pp 196–210.
10. T. Gorschek et al., "A Model for Technology Transfer in Practice," IEEE Software, vol. 23, no. 6, 2006, pp. 88–95.
11. A. Van den Ven, Engaged Scholarship: A Guide for Organizational and Social Research, Oxford Univ. Press, 2007.
12. A. Borjesson et al., "Continuing Professional Development by Practitioner Integrated Learning," Companion to 22nd ACM SIGPLAN Conf. Object Oriented Programming Systems and Applications (OOPSLA 07) Educator's Symp., ACM Press, 2007, pp. 897–907.
13. M. Staron, W. Meding, and C. Nilsson, "A Framework for Developing Measurement Systems and Its Industrial Evaluation," Information and Software Technology, vol. 51, no. 4, 2008, pp. 721–737.
14. T. Arts et al., "Testing Telecoms Software with Quviq QuickCheck," Proc. 2006 ACM SIGPLAN Workshop on Erlang, ACM Press, 2006, pp. 2–10.
SEARCH
22 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool