Work on the system SCRUM
Scrum http://ru.wikipedia.org/wiki/Scrum - methodology of the development management of information systems for Agile Software Development. Scrum clearly focuses on quality control of the development process. By-turn, this system is a part of the systems and principles of Agile http://ru.wikipedia.org/wiki/Agile, which professes openness and aiming on the final product, in the first place it states the task in satisfaction of just users` needs. Due to ongoing work with the remote personnel and the remote client , the company 5-SOFT went to work on the system SCRUM.
What it is and how it works:
Scrum is a set of principles on which the development process is drawing, allowing a small hard fixed time intervals (sprints from2 to 4 weeks) to provide end-user working software with new features, which the highest priority indentified for. Software Features to be implemented in the next sprint, are determined at the beginning of the sprint at the planning stage and can not be modified in its entirety. In this strictly fixed small duration sprint makes the process of developing predictability and flexibility.
The main functional roles in Scrum are
- Scrum Master is the one who leads Scrum meetings and makes sure that all the principles of Scrum are respected (role does not assume anything but the correct maintenance of Scrum itself, project manager rather refers to the Product Owner and should not be a Scrum Master);
- The owner of the Product (Product Owner)is a person who represents the interests of end users and other interested in the product parties;
- Cross functional team (Scrum Team), consisting of both developers and testers , architects, analysts, etc. (herewith the size of the team, ideally, is 7 ± 2 persons). The team is the only fully involved participant in the development, and it is responsible for the result as a whole. Nobody but a team can interfere in the development process for the sprint.
During each sprint, 15-30 day period (duration is determined by the team), it is created a functional growth of the software. The list of features that are implemented in each sprint comes from the stage, called the product backlog (documentation of requests for perform works), which is the highest priority in accordance with requirements for the work to be performed. Requests for fulfillment of works (backlog items), defined on the Planning Board for the sprint (sprint planning meeting), are moved to the sprint stage. During this meeting the Product Owner informs about tasks that must be carried out .Then the team determines how much of the desired they can perform to complete the necessary parts for the next sprint. During the sprint, the team performs a fixed list of tasks ( so-called sprint backlog). During this period, no one has the right to change the list of requirements for the work that must be understood as freezing requirements during the sprint.
Thus, thanks to this system, we get a clear view of the current project on the customer’s side. The customer, on his side, can painlessly make revisions and corrections in the intermediate stages. And also to pay installments, provided for each module at the end of each sprint. He can always stop the development of the project at any time with the least financial losses for himself and financial losses for developers. This system is useful when the development of a global project is led by several teams of developers. In this case, the customer is incomparably difficult to track progress and compare the results and timing of each team and the deadline for implementation. But thanks to SCRUM he will have a clear and agreed terms, and he will also know exactly what is in these terms will be provided by each of teams. That will help the customer to make more definitive predictions for the final release of the product.