Please enable JavaScript.
Coggle requires JavaScript to display documents.
Scrum Vs XP | Differences and Similarities - Coggle Diagram
Scrum Vs XP | Differences and Similarities
At present, it is of vital importance to create strategies that contribute to the launch of software products aimed at the early delivery of tangible results.
Based on the foregoing, on February 17, 2001, at the request of Kent Beck, seventeen meet experts in software models based on processes
The result of this meeting was a document containing the four postulates called “Agile Manifesto"
Among these proposals is Scrum and XP as widely applied methodologies and widespread both in academia and in companies and development departments
In 1994 they obtained the following results in 50,000 projects studied:
• Percentage of projects that are canceled 31%.
• Percentage of problematic projects 53%.
• Percentage of successful projects 16%
Agile Origins
Although an attempt is made to follow a model for the software development problems will always arise that damage the project and many of the tasks that are made of time estimation and planning are usually in vain, they turn out to be repetitive tasks that extend the projects
On 2001 met in Utah a group of seventeen recognized development professionals of software, and referents of the methodologies light existing at the moment in order to give a stop traditional practices
It was like that The Agile Alliance, a non-profit organization, was created lucrative who simply wanted to promote the values and principles of the agile philosophy through something called the Agile Manifesto
General Characteristics of "Agilism"
Adaptable
Light
Easiness to Change
Reactive
Scrum
Scrum is a methodology for developing iterative and incremental software, owes its name to the rugby play called in the same way, is says that it is iterative since it is executed in blocks short and fixed temporary
Roles: Scrummaster, Product Owner, Team
Artifacts: Product Backlog, Sprint Backlog, Burndown chart, Sprints
XP
eXtreme Programming or XP is a methodology software development that adapts to the postulates of the Agile Manifesto prioritizing the adaptability and not following a plan
Common Practices
Pair programming
Colective Code Appropriation
Informative Workspace
Coding Standards
Sustainable March
Continious Integration