Academic journal article Journal of Economics & Management

The Critical Factors of Scrum Implementation in IT Project - the Case Study

Academic journal article Journal of Economics & Management

The Critical Factors of Scrum Implementation in IT Project - the Case Study

Article excerpt


The aim of the paper is to present critical factors of a successful implementation of the Scrum method, based on an example of one of IT companies. The Scrum method is the most popular and the most rapidly growing method among the agile methodologies: 56% of agile practitioners use Scrum in their projects [VersionOne 2015, p. 9]. Agile approach means, generally, more flexible project planning and execution, with more emphasize on the constant contact with the customer, which in most cases leads to a higher customer satisfaction [PMBoK 2013; Goldman, Nagel & Preiss 1995; Highsmith 2002; MacCormack 2001, pp. 75-84; Manifesto for Agile Software Development 2001]. In traditional way of project management, the process of product development was divided into some sequential phases. In this model, the customer defined all requirements at the beginning of development process. Agile methods (for e.g. Scrum) are excluded sequential of phases in project and focus on relationship with customer [Takeuchi, Nonaka 1986; Schwaber & Sutherland 2013].

Using literature review and the case study method, the authors of this paper attempted to analyze the factors which may help or disturb in the introduction of the Scrum in an organization and propose a model of their classification.

The paper consists of five sections. The first one is the introduction. The second one presents a review of the current knowledge about Scrum and classification of critical factors of agile methodologies implementation. The third and the fourth sections show our research method and findings. The identified critical factors are described, basing on the proposed model. The last section is composed of conclusions.

1.Theoretical background

This section present review of the literature, to present current knowledge of researched field of study. The Scrum method and models of classification of critical factors for implementation of agile methodologies are described. Finally, the proposed by authors model of classification is presented.

1.1.Scrum method

The Scrum was presented in 1995 by Ken Schwaber at OOPSLA conference in Austin [Rubin 2013], but foundations of Scrum were appearing in the eighties [Pham & Pham 2012; Rubin 2013]. Schwaber & Sutherland [2013] suggested that a key to success in Scrum is descended from experiences and create vital part of know how in company.

The Scrum is based on the empiricism, which is achieving by some qualities. Surveyed the literature on, the qualities, which build empiricism in Scrum are a clarity in each process, an inspection to detect problems in project and an adaptation to change [Schwaber & Sutherland 2013].

Scrum consists of three main elements, which are presenting below [Schwaber & Sutherland 2013, pp. 4-15]:

1. Roles - there are four main roles: (1) The Scrum Team - consist of Scrum Master, Development Team and Product Owner. (2) The Scrum Master - the person, who is responsible for understanding and using the values and rules of Scrum by Development Team and Product Owner. The main duties of Scrum Master is to serve for Scrum Team to achieve project aims. Scrum Master is not traditional manager, she/he is more like a counselor, who build the relationship with team members based on trust and cooperation [Schwaber 2004]. (3) The Product Owner - the person who knows the business case associated with the project. The main duties of Product Owner is to control the Product Backlog. Schwaber, Sutherland [2013] emphasize that Product Owner should have a decision-making power to make decisions on behalf of company. (4) The Development Team - developed the product according to requirements. Development Team is 'self-organizing', which means that it has a high degree of autonomy.

2. Artifacts - are the material or immaterial results of the work. In the literature, the authors reefers to: (1) Product Backlog - determines scope and list of features which should be implemented during the project. …

Search by... Author
Show... All Results Primary Sources Peer-reviewed


An unknown error has occurred. Please click the button below to reload the page. If the problem persists, please try again in a little while.