Scrum
Printer Friendly Format
Bookmark this page
Back to "Procedural model (software)"Scrum is a collection of work engineerings, structures, roles and methods for the project management in the context of agiler software development. It is a procedural model, which meets few definitions. Teams and/or developers organize themselves to a large extent and select also the assigned methods. The procedure and the methods are adapted to sequentially current requirements.
Basic assumptions
With Scrum it is in principle accepted that product manufacturing and development processes are so complex that they leave themselves in advance neither into large final phases, still into individual work procedures with the of days or hours per coworker before-flat. Thus it is more productive, if a team within a firm outside framework with very rough organizes itself. This organized team takes the common responsibility for the completion of the self-chosen task packages in this, with the Product Owner co-ordinated, framework. Traditional tools, e.g. for communication or steering of the project as well as by the management "from above ", are rejected of processes fixed for the team structuring, which control and adjust co-operation in the team.
The following plakativ formulated values appear in Scrum philosophy:
- Individuals and interactions are considered more than processes and Tools.
- Functioning programs are considered more than detailed documentation and beautiful architectures.
- Constant co-operation with the customer stands over contracts.
- The courage and openness for changes stand over obeying a fixed plan.
Scrum roles
With Scrum there are three clearly separated roles, which are implemented by coworkers, who work on the same project together and so that also have the same goal. So that everyone is responsible for what it can do, and responsible, the competencies are divided as follows:
| Role | Task |
|---|---|
| Product Owner | The Product Owner specifies the common goal, which must reach the team. It makes the budget available. It constantly supervises the capital net yield. It sets regularly the priorities of the individual Product Backlog elements and supervises successes and expenditures. The Product Owner specifies finally the official version of the product, and takes over release management. |
| Team | The team estimates would wind up the individual baking logs elements off, and begins with the implementation of the elements creatable for the next Sprint. In addition before the Begin of the Sprints a further planning meeting is accomplished, with which the elements of the Backlogs and concrete tasks are divided. The team works organized in the context Time of a box (the Sprint), and has the right (and the obligation), to even decide after the next Sprint to be achieved to have, one speaks how many elements of the Backlogs thereby of commitments. |
| Scrum master | The Scrum master has the task to accomplish the processes of the development and planning and to supervise the allocation of the roles and rights. It keeps transparency upright during the entire development, and promotes that adds the existing improvement potentials. It is not under any circumstances responsible for communication between team and Product Owner, since these communicate directly with one another. It stands for the team to the side, is however neither Product Owner nor part of the team. The Scrum master ensures with all means for the fact that the team is productive, the conditions of work is thus correct and the team members is content. |
During the allocation of role it was considered that the team organized itself. The Product Owner does not give, which team member makes when which and whom zuarbeitet. With Scrum from the assumption it is proceeded that the team organizes itself intuitively, and to each task dynamically a bestangepasste internal organisational structure forms, which adapts relatively fast to the changing complex tasks. The Scrum master has the obligation to make certain that the products Owner does not intervene in this adaptive self organization process and disturbs the team or actually takes responsibilities, which are not entitled to it.
Product baking log
The Product baking log contains the features of the product which can be developed. It contains all functionalities, which the customer wishes, plus technical dependence. Before each Sprint the elements of the Product Backlogs are again evaluated, existing elements can be added far away as well as new.
Sprint
Central element of Scrum is the Sprint . A Sprint calls the conversion of an iteration, Scrum suggests approx. 30 days iteration length. Before the Sprint the product requirements of the customer in a so-called product baking log are collected. Also technical and administrative tasks are taken up there. The product baking log must be not complete; it is constantly continued. The requirements for the first Sprint are mostly rapidly set up. The requirements are outlined informal. Provided for a Sprint a Sprint Backlog will become, transferred to these requirements, which are to be converted during the Sprints. The decision, which requirements are converted, is made by the customer after priorities specified by it. To the Sprint organize yourself the development team, need thus no detailed methodical regulations. The requirements from the Sprint Backlog are divided by the team, each developer estimate and evaluate him assigned tasks.
Scrum Meeting
On each day a short Scrum Meeting takes place. The term originates from the language of the Rugby sport and means '' crowding '' (Rugby). Each developer reports his current working progress since the past Meeting and makes promises for the results up to the next Meeting. Arisen problems are clarified after the Meeting. The daily Kurzmeetings serves for the change of information in the team and additionally for disciplining. Developers feel usually bound to the promises given in the Scrum Meeting. Optimal time for the Scrum Meeting is the time after the lunch, since morning Scrum Meetings with flexible Gleitzeitregelungen to often collide and the tired point falls after the lunch with a Scrum Meeting, which can be quite held in standing, not as strongly important as with other activities. The Meetings are shorter than in the morning, because general things and pieces of news were discussed already before. The coworkers are already busy for the work and not still their private problems at noon with the head.
Larger projects can be modularized. Then by the respective directors/conductors of the subprojects a Scrum OF Scrum Meeting is accomplished, with which the results of the individual groups are summarized.
Review
During the Sprints the requirements from the Sprint Backlog may not be changed. The team can concentrate therefore unimpaired on the conversion. After a Sprint the Sprint result is submitted to an informal Review by team and customer. In addition the result of the Sprints (the current software) will become demonstrated, possibly technical characteristics presented. The customer examines, whether the Sprint result corresponds to its requirements, possible changes in the product baking log is documented.
Literature
Ken Schwaber, Mike Beedle: Agile software development with Scrum. To Prentice resound, 2001, ISBN 0-13-067634-9
Related links
- Ken Schwabers Web Site (particularly useful: the vocabulary under left "Resources")
- Jeff Sutherlands Web Site
- Scrum of courses in Europe (scrumeducation.com)
- Scrum Yahoo group into German
- Mike Cohns Web Site
Back to topRelated Websites
We found here 5 related websites.
- About Scrum - Overview
Scrum is an agile process to manage and control development work. ... Scrum is a way for everyone to feel good about their job, their contributions, ... - Scrum (management) - Wikipedia, the free encyclopedia
Scrum was first documented by Takeuchi and Nonaka in "The New New Product ... Although scrum was intended to be for management of software development ... - Scrum (management) - Wikipedia, the free encyclopedia
Scrum was first documented by Takeuchi and Nonaka in "The New New Product ... Although scrum was intended to be for management of software development ... - Scrum Development Process
The Scrum homepage, information on the methodology, implementation, project management and free tools. - Scrum.com
scrum.com brings you all the latest action from the Rugby World Cup 2003, Zurich Premiership, BT Scottish Premiership, Welsh Premiership, Heineken Cup, ...
Index | Privacy | Terms Of Use | Sitemap | Feedback
