Introduction to SCRUM Methodology

SCRUM Agile methodology is one of the most famous project or program management methodologies. Agile methodology is a new methodology of software development and has many advantages compared to the classical methods.

The Scrum methodology is iterate (the product is produced during the small cycles called iterations), incremental (the functionality of the product increase during each iteration by adding new properties) and use its own terminology for working people and some procedural steps.
Scrum methodology have many elements but none of them is random and unnecessary. There is a project team consisted of the owner of the product , ScrumMaster and Scrum team. Each one have different task to perform.

The entire Scrum process is also divided. There are following phases: pregame, game and postgame. The structure of the Scrum methodology is very complex but not complicated!

Scrum is a process template commonly used to oversee projects, and manage complex work. Typically it is complemented by agile software development, encouraging teamwork and self-organization. The name itself is influenced by "scrums" in terms of the game of rugby. The name reflects the nature of what is achieved through the method, in terms of group members all successively striving towards better work efficiency.

Scrum Methodology - Quick Introduction

Scrum is a repetitive framework for software and product development. It can be compared to a game - company is a team owner, employees are team players and the game itself is desired product waiting to be enhanced. When the game is on we can clearly see what is wrong and what is acceptable. Scrum methodology is a way to spot deficiency and improve. Scrum methodology shows how to play the game and sets some ground rules. Scrum helps to coordinate massive production process - especially when company has many "teams" and control is essential.

During the Scrum process faults are uncovered but the process itself is time-consuming. First step is to divide work force into small teams and make them learn how to cope with each other. Second step is to improve skills of the "players". First part takes about a year to conduct, second part - little bit longer, about three to five years. Then Scrum methodology shows results, which is exposing flaws in development, correcting them and process again and again until the product is flawless.

Scrum methodology considers inevitably that certain obstacles are on the way to perfection during production process. These random obstacles cause long-term plans useless, so Scrum proposes to induce cycle-like project, introducing Sprints, to overcome any difficulties in the race towards the final goal.

Having such problems as too high costs of production, non-functionality, customers leaving your company to other vendor leads to certain point where you might consider using Scrum to improve those aspects. Scrum also provides serious amount of help in building projects.

Some basic questions

What is a methodology?

Methodology can be defined in different ways. Usually if we look into any encyclopedia we will find a definition that it looks for the best approach to problems solving. In terms of programming methodology, it is looking for the best ways of developing software systems.

What is the SCRUM methodology?

Scrum is a software development methodology which consists of:

  • Management methodology
  • Enhancement methodology
  • Maintenance methodology

What is the difference between agile methodology and other, traditional methodologies?

Agile methodology emphasizes the communication ,collaboration ,rapid exchange of information , teamwork and what is very important the functioning software and flexibility(adaptability to the changing development factors and external environment). Software development process is sometimes very unpredictable and might be complex.

If all developers worked communicated and collaborated together, it will be easier to create better software. Because of that the agile methodology is the best solution for projects with rapidly changing, hard and emergent requirements.
While the agile methodology is focused on people the traditional methodology is focused on processes , sequence of processes and useful tools. It is flexible but only in the beginning of the project and doesn’t handle appropriate with changing environmental needs and requirements after the start.

What are the benefits of the SCRUM methodology?

The benefits are on both sites. The client is happy because they received what they needed and expected. For developers the benefits of taking a part in Scrum methodology are more subjective – it might be his/her motivation and satisfaction of making the work done, in an efficient fashion.

The history of SCRUM methodology

The short history of SCRUM methodology with the most important dates:

  • In 1986 Hirotaka Takeuchi and Ikujiro Nonaka described a new approach to the product development in which all the phases of the process overlap and the team work together across the different phases.
  • In 1991 DeGrace and Stahl in “Wicked Problems , Righteous Solutions” referred to this approach as Scrum(term of rugby).
  • In the early 1990s the Scrum methodology was introduced into some companies f.ex by Ken Schwaber and it was for the first time called SCRUM by Jeff Sutherland, John Scumniotales, and Jeff McKenna.
  • In 1995 Sutherland and Schwaber described Scrum and presented the results at OOPSLA in Austin.
  • 2001 “Agile Software development with Scrum”-book written by Ken Schwaber and Mike Beedle.