Scrum Methodology in Agile Software Development

From apppm
Revision as of 12:50, 21 September 2015 by S150821 (Talk | contribs)

Jump to: navigation, search

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

Main figures in Scrum

Product Owner

Development Team

Team self-organization

Scrum Master

Application

Sprint

Sprint Planning meeting

Daily Scrum and Sprint execution

Sprint review meeting

Sprint retrospective meeting

Backlog Refinement meeting

Artefacts

Product Backlog

Product Backlog Item (PBI)

Sprint backlog

Sprint task

Sprint Burndown Chart

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox