Advertisement

Organizational Enablers for Agile Adoption: Learning from GameDevCo

  • Jayakanth Srinivasan
  • Kristina Lundqvist
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 31)

Abstract

Adopting agile methods requires an understanding of both the mechanics and the dynamics of value creation in software organizations. From a mechanics perspective, successful agile adoption is about ensuring that project stakeholders are aligned toward a common project objective, employees have the ability to make decisions at the right level of abstraction, that there is effective project management, and an environment exists that supports individual and group learning. The dynamics of value creation require an understanding of organizational-level stakeholders and their value propositions, the development of an organizational learning system, and last but not least, an effective governance strategy. This paper uses the lessons learned a case study of GameDevCo to illustrate these organizational enablers for agile adoption.

Keywords

Agile Adoption Case Study Engaged Scholarship Enablers 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Ngwenyama, O., Nielsen, P.A.: Competing values in software process improvement: an assumption analysis of CMM from an organizational culture perspective. IEEE Transactions on Engineering Management 50(1), 100–112 (2003)CrossRefGoogle Scholar
  2. 2.
    Teece, D.J., Pisano, G., Shuen, A.M.Y.: Dynamic Capabilities And Strategic Management. Strategic Management Journal 18(7), 509–533 (1997)CrossRefGoogle Scholar
  3. 3.
    Zollo, M., Winter, S.G.: Deliberate Learning and the Evolution of Dynamic Capabilities. Organization Science 13(3), 339–351 (2002)CrossRefGoogle Scholar
  4. 4.
    Ethiraj, S.K., Kale, P., Krishnan, M.S., et al.: Where do capabilities come from and how do they matter? A study in the software services industry. Strategic Management Journal 26(1), 25–45 (2005)CrossRefGoogle Scholar
  5. 5.
    Athreye, A.S.: The Indian software industry and its evolving service capability. Industrial and Corporate Change 14(3), 393–418 (2005)CrossRefGoogle Scholar
  6. 6.
    Ono, T.: Toyota Production System: Beyond Large-Scale Production. Productivity Press (1988)Google Scholar
  7. 7.
    Spear, S., Bowen, H.K.: Decoding the DNA of the Toyota Production System. Harvard Business Review 77, 96–108 (1999)Google Scholar
  8. 8.
    Sugimori, Y., Kusunoki, K., Cho, F., et al.: Toyota production system and Kanban system Materialization of just-in-time and respect-for-human system. International Journal of Production Research 15(6), 553–564 (1977)CrossRefGoogle Scholar
  9. 9.
    Liker, J.K., Meier, D.: Toyota Talent: Developing Your People the Toyota Way. McGraw-Hill, New York (2007)Google Scholar
  10. 10.
    Morgan, J.M., Liker, J.K.: The Toyota Product Development System: Integrating People, Process, and Technology. Productivity Press (2006)Google Scholar
  11. 11.
    Roth, G., Labedz, C.: Lean Enterprise Change Case Study: Rockwell Collins. MIT, Cambridge (2006)Google Scholar
  12. 12.
    Heeks, R., Krishna, S., Nicholson, B., et al.: Synching or Sinking: Global Software Outsourcing Relationships (2001)Google Scholar
  13. 13.
    Van de Ven, A.H.: Engaged Scholarship: A Guide for Organizational and Social Research. Oxford University Press, USA (2007)Google Scholar
  14. 14.
    Boehm, B., Bose, P.: A collaborative spiral software process model based on Theory W, pp. 59–68Google Scholar
  15. 15.
    Boehm, B.: Anchoring the software process. IEEE Software 13(4), 73–82 (1996)CrossRefGoogle Scholar
  16. 16.
    Clements, P., Garlan, D., Little, R., et al.: Documenting software architectures: views and beyond, pp. 740–741Google Scholar
  17. 17.
    Damian, D.: Stakeholders in Global Requirements Engineering: Lessons Learned from Practice. IEEE SOFTWARE, 21–27 (2007)Google Scholar
  18. 18.
    Damian, D.E., Zowghi, D.: The impact of stakeholders’ geographical distribution on managing requirements in a multi-site organization, pp. 319–328Google Scholar
  19. 19.
    Beck, K.: Extreme programming explained: embrace change. Addison-Wesley Longman Publishing Co., Inc., Boston (1999)Google Scholar
  20. 20.
    Boehm, B., Turner, R.: Using Risk to Balance Agile and Plan-Driven Methods. Computer, 57–66 (2003)Google Scholar
  21. 21.
    Randolph, W.A.: Re-thinking empowerment: Why is it so hard to achieve? Organizational Dynamics 29(2), 94–107 (2000)CrossRefGoogle Scholar
  22. 22.
    Conger, J.A., Kanungo, R.N.: The empowerment process: integrating theory and practice. Academy of Management Review 13(3), 471–482 (1988)Google Scholar
  23. 23.
    Pfeffer, J.: Organizations and Organization Theory, Cambridge, MA (1982)Google Scholar
  24. 24.
    Burke, W.: Leadership as empowering others. Executive power, 51–77 (1986)Google Scholar
  25. 25.
    Aoyama, M.: Web-based Agile software development. IEEE Software 15(6), 56–65 (1998)CrossRefGoogle Scholar
  26. 26.
    Dyba, T.: An Instrument for Measuring the Key Factors of Success in Software Process Improvement. Empirical Software Engineering 5(4), 357–390 (2000)CrossRefGoogle Scholar
  27. 27.
    Baddoo, N., Hall, T.: Motivators of Software Process Improvement: an analysis of practitioners’ views. The Journal of Systems & Software 62(2), 85–96 (2002)CrossRefzbMATHGoogle Scholar
  28. 28.
    Quinn, R., Spreitzer, G.: The road to empowerment: seven questions every leader should answer. Organisational Dynamics 26(2), 37–50 (1997)CrossRefGoogle Scholar
  29. 29.
    Ashforth, B.E.: The experience of powerlessness in organizations. Organizational Behavior and Human Decision Processes 43(2), 207–242 (1989)CrossRefGoogle Scholar
  30. 30.
    Rus, I., Lindvall, M.: Knowledge Management in Software Engineering. IEEE SOFTWARE, 26–38 (2002)Google Scholar
  31. 31.
    Basili, V.R., Caldiera, G., Rombach, H.D.: Experience Factory. Encyclopedia of Software Engineering 1, 469–476 (1994)Google Scholar
  32. 32.
    Ruhe, G., Bomarius, F.: Learning software organizations. Springer, New York (2000)CrossRefGoogle Scholar
  33. 33.
    Schneider, K., von Hunnius, J.P., Basili, V.R.: Experience in Implementing a Learning Software Organization. IEEE SOFTWARE, 46–49 (2002)Google Scholar
  34. 34.
    Althoff, K.D., Bomarius, F., Tautz, C.: Knowledge Management for Building Learning Software Organizations. Information Systems Frontiers 2(3), 349–367 (2000)CrossRefGoogle Scholar
  35. 35.
    Dyba, T.: Improvisation in small software organizations. IEEE Software 17(5), 82–87 (2000)CrossRefGoogle Scholar
  36. 36.
    Sawyer, S., Guinan, P.J.: Software development: Processes and performance. IBM Systems Journal 37(4), 552–569 (1998)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Jayakanth Srinivasan
    • 1
  • Kristina Lundqvist
    • 1
  1. 1.Mälardalen UniversityVästeråsSweden

Personalised recommendations