RESEARCH PAPER

“Scrum by Itself Is Never Enough” - Research Paper



Abstract

This paper investigate the challenges and critical issues that may occurs in Scrum agile process of the software development and gives management procedure to help out organizations keep away from in addition to overcome hurdles in accepting Scrum method as a prospect software development technique. This paper also comments on the statement “Scrum by itself is never enough” including critical analysis of this statement. The paper discusses and assesses the relevant issues and also the recommendation that it may be used in conjunction with other methods for the betterment.

Table of Contents

Introduction4

Discussion5

Comment on the Statement5

Problems and Issues7

Recommendations10

Using Scrum in Conjunction with Other Methods11

Conclusion13

Methods and Modelling Coursework - Research Paper

Introduction

An agile process of software development is the Scrum, which can be utilized to control and manage complex product and software development using incremental and iterative practices and is a development of incremental and iterative approach to deliver software that is objected-oriented. The term “Scrum” arrives from the well known sport Rugby, fifteen players in two teams struggle next to each other. Nonaka and Takeuchi initially used strategies of rugby to explain the processes of hyper productive in Japan. The approaches which come from the sport are a holistic squad approach, continuous interaction among the members of team, and static core members of the team are accepted into the Scrum control and management process (Williams, 2003, pp. 39-43).

Besides the several benefits or advantages of these agile methods, a number of organizations and businesses are unwilling to replace their conventional methods and move to agile method. Their unwillingness is the consequence of more than a few issues, that may includes the agile methods that considerably decrease the documentation and heavily rely on implicit knowledge, one of the issues associated with this is the methods are not adequately tested intended for safety-critical projects or missions, and the next is the faith that such methods are insufficient for projects that are highly stable, including a fear that these new methods be able to successful just with talented persons who favor several degrees of liberty, and that methods are inappropriate for the projects of large-scale (Watson, 1997, pp. 91-115).

Due to these and several other issues the statement seems somewhat true that the Scrum is itself not enough. Continuous integration has to be utilsed to validate the system's state. Testing should be functional at the system, unit and recognition level. Automating the testing will give feedback that will facilitate the team being agile. On the other hand if these tests are not automated, the manual testing may turns out to be a bottleneck over the passage of time and in a result of that slowing the whole team down.

The aim is a critical analysis of the statement “Scrum by itself is never enough” and investigation of the relevant issues regarding the Scrum and recommendations for using the Scrum with other methodologies.

Discussion

Scrum is a widely used, outstanding software development all over the ...