The Critical Factors of Scrum Implementation in IT Project - the Case Study
The paper first presents basic information about the Scrum method. Then it summarizes the state of art in the domain of Scrum implementation, especially as far as the critical factors of its success are concerned. On the basis of literature survey a new model classifying Scrum implementation critical factors is proposed. The model divides Scrum implementation critical factors into five categories: Project Team factors, Psychological and cultural factors, Process and Method, Environment and Technology. The model is then developed and verified using the case study method. The research was carried out in a French IT company by means of a participating observation. The company was implementing Scrum, which ended up as a success. A journal of the Scrum implementation was conducted, presenting the experiences of the Scrum Team, their opinions and changes in the Scrum method which were introduced. On its basis critical factors, crucial for the success of Scrum implementation, classified according to the above mentioned model, were identified, completing those which had been found in the literature.(original abstract)
- A Guide to the Project Management Body of Knowledge (PMBoK Guide) - Fifth Edition (2013). Project Management Institute, Newtown, PA.
- Boehm B., Turner R. (2005): Management Challenges to Implement Agile Processes in Traditional Development Organizations. "IEEE Software", Vol. 22, pp. 30-39.
- Chow T., Cao D.B. (2008): A Survey Study of Critical Success Factors in Agile Software Projects. "The Journal of Systems and Software", Vol. 81, pp. 961-971.
- Goldman S., Nagel R., Preiss K. (1995): Agile Competitors and Virtual Organizations: Strategies for Enriching the Customer. Van Nostrand Reinhold, New York.
- Greene R.T. (1993): Global Quality: A Synthesis of the World's Management Methods. ASQC Quality Press, Milwaukee.
- Highsmith J. (2002): Agile Software Development Ecosystems. Addison Wesley, Boston.
- MacCormack A. (2001): Product-Development Practices that Work: How Internet Companies Build Software. "MIT Sloan Management Review", Vol. 2, pp. 75-84.
- Manifesto for Agile Software Development (2001), http://www.agilemanifesto.org/ (access: 8.05.2016).
- McHugh M., McCaffery F., Casey V. (2012): Barriers to Adopting Agile Practices when Developing Medical Device Software. "Communications in Computer and Information Science", Vol. 290, pp. 141-147.
- Nerur S., Mahapatra R.K., Mangalaraj G. (2005): Challenges of Migrating to Agile Methodologies. "Communications of the ACM", Vol. 48, pp. 72-78.
- Ozierańska A. (2015): Wdrażanie metod zwinnych na przykładzie średniego przedsiębiorstwa informatycznego. Master Thesis, Wrocław Univeristy of Science and Technology, Faculty of Computer Science and Management, Wrocław.
- Pham A., Pham P. (2012): Scrum in Action: Agile Software Project Management and Development. Course Technology PTR, Boston.
- Rola P., Kuchta D., Kopczyk D. (2016): Conceptual Model of Working Space for Agile (Scrum) Project Team. "Journal of Systems and Software", Vol. 118, pp. 49-63.
- Rubin K.S. (2013): Scrum: Praktyczny przewodnik po najpopularniejszej metodyce agile. Helion, Gliwice 2013.
- Schwaber K. (2004): Agile Project Management with Scrum. Microsoft Press, Redmond, WA.
- Schwaber K., Sutherland J. (2013): Scrum Guide. The Definitive Guide to Scrum: The Rules of the Game. http://www.scrumguides.org (access: 8.05.2016).
- Takeuchi H., Nonaka I. (1986): The New New Product Development Game. "Harvard Business Review", No. 1, pp. 137-146.
- VersionOne (2015): 9th Annual The State of Agile Survey. VersionOne, No. 9, Alpharetta, GA.