Scrum Methodology in Agile Software Development
(→Scrum methodology) |
|||
| Line 9: | Line 9: | ||
==Agile Software Development== | ==Agile Software Development== | ||
=Scrum methodology= | =Scrum methodology= | ||
| + | There are two concepts that are at the basement of Scrum methodology: '''iterative development''' and '''team working'''. Developing in iterations allow Scrum team to adapt quickly to changing requirements, while working in close location and focusing on communication allow team to make decisions and act on them immediately rather than wait on correspondence. | ||
| + | |||
| + | Basically Scrum consists in a sequence of fixed-length iterations called '''Sprints''' managed by one or more '''cross-functional and self-organizing teams''' each composed by seven people that aim at a common goal and that usually work only on the software development. There are instead other two figures that manage all things that are in support of the development process: one is '''Product Owner''' who mainly handles customers contacts and the other is '''Scrum Master''' whose main task is to ensure that development team can work without obstacles. | ||
| + | |||
| + | Each sprint usually lasts from 2 to 4 weeks, in this period there are at least one meeting between the Product Owner and Development Team to define the main objectives; then there are short daily meetings held every morning to enhance communication and inform customers, developers, and managers on the status of the project, identify any problems encountered, and keep the entire team focused on a common goal. | ||
| + | |||
==Main figures in Scrum== | ==Main figures in Scrum== | ||
===Product Owner=== | ===Product Owner=== | ||
Revision as of 13:12, 21 September 2015
Today market is affected by uncertainly and sudden changes, in these conditions most of the models used in the 20th century to develop software are not still appropriate. Waterfall model , probably the most famous between them, is characterized by a stiff structure which can’t cope with the turbulent needs of actual market. In recent years many innovations are been enhanced in software engineering with a particular focus on the flexibility of these methods in order to cope with the customer’s and market’s needs; surely Agile Software Development is between them; ASD embraces the principles of lean production by applying them in software development to avoid waste and increase responsiveness to change. It represents the solution to the unpredictability of the market where the capacity to welcome change even late in development to satisfy customers is required. This article deals with Agile Software Development with a particular focus on one of its most used technique : Scrum Methodology.
Contents |
The big Idea
History: from Waterfall model to Agile Software Development
Waterfall model
Iterative model
Agile Software Development
Scrum methodology
There are two concepts that are at the basement of Scrum methodology: iterative development and team working. Developing in iterations allow Scrum team to adapt quickly to changing requirements, while working in close location and focusing on communication allow team to make decisions and act on them immediately rather than wait on correspondence.
Basically Scrum consists in a sequence of fixed-length iterations called Sprints managed by one or more cross-functional and self-organizing teams each composed by seven people that aim at a common goal and that usually work only on the software development. There are instead other two figures that manage all things that are in support of the development process: one is Product Owner who mainly handles customers contacts and the other is Scrum Master whose main task is to ensure that development team can work without obstacles.
Each sprint usually lasts from 2 to 4 weeks, in this period there are at least one meeting between the Product Owner and Development Team to define the main objectives; then there are short daily meetings held every morning to enhance communication and inform customers, developers, and managers on the status of the project, identify any problems encountered, and keep the entire team focused on a common goal.
