RSS
Логотип
Баннер в шапке 1
Баннер в шапке 2
2017/11/08 15:44:11

Scrum

Scrum (Scrum) — a project management methodology for agile development of the software. Unlike cascade approach where requirements are formalized and fixed at the very beginning of the project, use methodologists of Scrum allows the customer to change functional requirements and to properties of a system directly in the course of its development. When using methodology of Scrum development of the software product is conducted by small iterations (2-4 weeks). Upon termination of each of them the ready-made product is transferred to the customer, and priorities of development are analyzed and if necessary are reviewed. During each iteration all works on requirements gathering, design, coding and testing of a product are carried out.

Content

Scrum – the flexible (Agile) methodology of software development which is most extended in the market. Contrary to the traditional "principle of falls" according to which all system is given to the customer at the same time at the very end of the project process of Scrum is constructed in such a way that the development team gradually adds functionality to a system, working with rather short iterations, and with a certain frequency hands over to the customer the working code having actual value for business. Thereby project risks are minimized and return increases by investments. Extensive researches show what in case of correct application of Scrum helps to reach a considerable gain of labor productivity of programmers, even during the work of the big commands participating in large-scale, globally distributed projects.

2017: New version of the guide to Scrum

On November 7, 2017, Ken Shvaber and Jef Sutherland published the new version "Guides to Scrum". Preparation of the Russian-language version of the management was organized by Unusual Concepts company.

The main changes concerned areas where Scrum can be applied. The list is significantly expanded and added: now Scrum officially can be used absolutely everywhere if development goes in the conditions of uncertainty. Scrum can be applied in any industry. From 1993 for 2017 Scrum was applied in a huge number of different contexts:

  • management of the organizations (movement of the coauthor of the first book on Scrum and Manifesto Adzhayla of Mike Biddl Enterprise Scrum);
  • training (eduScrum the movement which even implemented the version "Guides to Scrum" for the training projects);
  • developments of the car;
  • marketing and sales;
  • management of professional development.

These contexts became so numerous that there was a need to expand a zone of applicability Scrum in the official description of a framework. In the new version of the Management there are such lines:

"Scrum was initially developed for development and product management and their development. Since the beginning of the ninetieth Scrum it is actively used worldwide that:
  • investigate and reveal the viable markets, technologies and possibilities of products;
  • develop products and improve them;
  • release products and their updates several times a day;
  • develop and support cloud computing (online, safely, on demand) and other environments for use of products;
  • support and update products.

Scrum was applied to software development, the equipment, the firm ware, autonomous vehicles and microbiological researches. Scrum was used at schools, the government, marketing, in management of the organizations — everywhere and daily in life of certain people and communities".

Scrum can be used at all stages of work on a product. It is important what the words "develop" and "development" which are often used in "The guide to Scrum", mean not only development, as well as a research, release, operation and support of any difficult products. It means that Scrum is suitable for any stage of work on a product.

Imagine the company at the very beginning of a way. There is no product yet, only a number of the assumptions which need to be checked. At this stage of Scrum it is possible to use as the engine for check of hypotheses, and constantly updated business model of future product will be result.

When the successful business model is found, Scrum can be applied to creation of the first version of a product. Then Scrum will be suitable for creation of updates and improvements of a product. The department of client support can work on Scrum too, then improvement of quality of service of support or improvement of documentation can be result of work as iterations.

Universal solutions do not happen: Scrum still does not suit for the enterprises of inline assembly, army and most state structures. But will help if in your work there is a lot of uncertainty, competitive market or it is necessary to create the innovation products. Here only a part of "indications" to application of the Scrum:

  • the market quickly changes, and demand often surprises you;
  • it is difficult to predict the end result, you constantly do not get to requests of clients;
  • it is a lot of changing factors: technologies, people, requirements to products;
  • you need speed to create products quicker than competitors;
  • you are busy with search of non-standard solutions.

If you have at least one of these "indications", it is necessary to try.

If you want to try the Scrum in operation and to get its advantages, define your product, and then start the Scrum engine. At the same time can be a product anything:

  • conference which you need to organize in half a year;
  • the forthcoming holiday with family;
  • apartment renovation;
  • you and your personal business model;
  • separate business unit which you manage;
  • company entirely.

Scrum is a framework which helps to create, release and support products in difficult conditions. Be not afraid to try it in unexpected contexts, authors of Scrum did not know how widely it will be applied. Years and a set of confirmations were required to be sure: it really works.

1995: Emergence of Scrum

Scrum appeared in 1995 as a framework which helped software developers quickly and to effectively develop the software. Process of Scrum was for the first time described in Jeff Sutherland and Ken Shvaber's article written for a conference in 1995.

Procedure of certification of Scrum-competence (Scrum Capability Assessment)

Assessment procedure of Scrum-competence is developed by Scrum Inc company. as tool of performance improvement and quality of development processes of software. It is the systematic consecutive process assuming a thorough research of all aspects of use of the principles and the practician of methodology of Scrum in the company and designed to be realistic about Agile-competence of specific project teams. As a result of scrupulous quantitative assessment of many tens of parameters of the company the total point of Scrum-competence is appropriated and also the detailed list of specific recommendations about improvement of development process and management is provided.

See Also