A Report On The Scrum

What makes Scrum different from other processes is the daily stand-up meeting referred to as "the Scrum" in which every team member should comment on the following three points (Krebs, J., 2005):

The Scrum master calls a sprint planning meeting that must be attended by the whole team and the product owner.

Ones the requirements are collected a target can be planned but it can also very difficult to know form the beginning how the project will be looking because changes are welcome in any stage of the development. Changes can occur during the development process which can change the whole process but is also very flexible. A strong developer and customer can be established during every iteration which can help to identify the user needs and make clearer about project and what the user actually wants from the project and what his or her expectations are. Faults can be detected in better because of the

Also in addition to my studies about Agile, I have made efforts to compare the same with another heavy weight methodology called Waterfall. Comparison include the strength and weakness of the two opposing methodologies and the outcome of a controlled empirical study conducted at Carnegie Mellon University in Silicon Valley by Feng Ji and Todd Sedano.

Agile is an iterative and incremental (evolutionary) approach to software development which is performed in a highly collaborative manner by self-organizing teams within an effective governance framework, with "just enough" ceremony, that produces high quality solutions, in a cost effective and timely manner which meets the changing needs of its stakeholders [1].

Scrum (link to the page http://en.wikipedia.org/wiki/Scrum_(software_development)) is a project management methodology. It is mostly used in I.T. and Software Development. Scrum is an iterative and incremental variant of Agile (link to http://en.wikipedia.org/wiki/Agile_software_development) Software Development Methodology that was created by Ken Schwaber (Link to http://en.wikipedia.org/wiki/Ken_Schwaber) and Jeff Sutherland (http://en.wikipedia.org/wiki/Jeff_Sutherland) in the 90's. S

Waterfall does have its issues: the process is generally “uni-directional” meaning that once the project hits a certain stage, there’s no mechanism to go back to a previous stage. This prohibits this method from being responsive to changing environments and/or requirements. The extensive documentation required at each stage (requirements, specification, design documentation, test plans and status) requires a great deal of time to complete. Additionally if it is discovered that there was a major issue with a missing requirement or the coding (and it’s uncovered in time) it is extremely expensive to make an adjustment.

The article "Using scrum in distributed agile development: A multiple case study" was a case study conducted with an interest toward proving the efficacy of scrum as a global software development approach (Paasivaara, Durasiewicz, Lassenius, 2009). The article makes little mention of XP as an approach, although it can be inferred that XP is also considered as a similarly useful method for increasingly distributed agile development. In order to explore the efficacy of scrum, the authors conducted a multiple case study involving three companies in Finland. The article begins with an introduction to scrum, and then discusses the methodology and results of the study. The authors found that scrum is a useful approach through which to succeed in the global economy, allowing companies to save money, communicate more efficiently, and coordinate the disparate offices that exist within a company.

As the technology develops swiftly, new harmonic approach to successful project has appeared. This report aims to briefly introduce the traditional and agile project management methodologies and differentiate these two concepts. The latter one is more flexible in dealing with changes during the project and it is an attitude rather than a process or a method. Moreover, the author illustrates some perspectives about the agile project management in a more detail way, which includes the core value and some critical principles in the agile project management. Besides, this report take the Scrum project as an example. It imposes the risk experience in Scrum implementation. After discussion, it suggests that risk planning and risk identification

Coexisting with other approaches :- There are many organization in which some project has moved to scrum and some has not. But according to author Mike Cohn and Scrum trainer Michele Sliger, Scrum and sequential can not coexist. Temporary existance is often necessary in large organization. If organization is trying to being agile, conflicts between two different method will be more painful. If the conflict's source are not removed, the organization will get back to the old software development method, and will be unable to get benefits of being

The world of technology is changing and advancing, in this day and age, faster than it ever has before. In order for businesses who create new technology and databases to not be left behind, they must find a way to better manage their groups in order to achieve upmost efficiency. Modern day tech managers can raise their effectiveness through the use of different processes, the first being agile project management, and the second being the scrum process. By using these processes group can ensure efficiency and effectiveness.

In this method, the team member is responsible for completing work and team determine how it can be completed smoothly(Scrum).

Perhaps one of the most glaring differences between Agile development approaches and other models like the waterfall approach is the sequentiality that exists in the latter method. In the waterfall method the projects start with a requirements planning stage,

“Agile Software Development is an umbrella term for a set of methods and practices based on the values and principles expressed in the Agile Manifesto. Solutions evolve through collaboration between self-organizing, cross-functional teams utilizing the appropriate practices for their context” (Agile Alliance, 2015).

Scrum technique does not provide any guidance how testing should be progressed. Hence scrum projects are usually divided into iterations also called as sprints. (Cervone 2011) Length of