Scrum is the second methodology of agile. The word scrum, the agile methodology derives from “rugby” where it’s mean restarting play after a rules infraction. Idea in agile The Scrum methodology is that a small team is unified around a single one goal. The idea in the agile Scrum-Methodology is that a small team is unified around a single goal and gets together for sprints of development that move them towards that goal.
In fact, Scrum mathodology is older than XP, with the original process management idea coming from Takeuchi and Nonaka’s 1986 paper, “The New Product Development Game.” Scrum first use is attribute to Stahl’s and De Grace 1990 book Righteous Solutions, Wicked Problems. The scrum is incorporates many features of XP and a variation on the iterative development approach.
The Scrum methodology has more management approach than XP. It does not define many detailed development practices that XP does. These practices use most scrum projects. More than 10 developers are not use in scrum teams. Although, most scrum projects will use these practices. Scrum agile methodology use teams of no more than 10 developers. Scrum emphasizes efficacy of collective ownership and small teams just like other agile methodologies.
The sprint that scrum is characterize, an iteration of between 1 and 4 weeks. In sprints, the fixed duration and output of a sprint is what work during sprint the team can accomplish. A sprint delivery date does not move out, it means sometimes a sprint can finish with less functionality and sometimes sprint can finish early than was proposed. A usable product always delivers by the sprint.
Two backlogs in which scrum requirements are encapsulate. The product owner and scrum team created the product backlog, which is prioritized list of all project requirements. Only the development team may add items to the sprint backlog, once the sprint start. During testing these are usually bugs found.
Scrum Master has facilitated scrum projects. Scrum Master is manage the backlogs, protect the team form outside influences during sprint and run daily scrum meetings. Usually, he is not a developer. Scrum projects have a daily stand – up meeting of 15 minutes to 30 minutes duration where sprint progress is discuss be entire team. The daily Scrum meeting permits the team to track sprint progress and share information.
Immediately By having these daily meetings, any problems in implementation or any slip in the schedule are obvious and once can then be address by the team. The Scrum master checks that everyone, tracks action items, at the meeting records the decisions made and makes progress. These meetings keep focused and short.
Scrum methodology is typically silent on development processes and is a project management methodology. Despite this, Scrum teams typically use many of the practices. In projects of scrum the common practices are Common code ownership, continuous integration, small releases, test – driven development, pair programming, simple design and coding standards.