Working of SCRUM

Scrum is an iterative and incremental framework for projects and product or application development. This is followed by many software development companies in India. It structures and manages development in cycles of work called Sprints. These iterations that are referred as sprints; are 1-4 weeks in length and take place one after the other sequentially. The Sprints are of fixed duration. They end on a specific date whether the work has been completed or not, and they are never extended. On top this, sprints are time boxed. 

At the beginning of each Sprint, a cross-functional team selects items (customer requirements or sprint scope) from a prioritized list. They commit and estimate to complete the items by the end of the Sprint. During the Sprint, the selected items or requirements do not change. Every day the team gathers briefly to report to each other on progress and update simple charts that orient them to the work remaining. At the end of the Sprint, the team reviews the Sprint with stakeholders and presents what they have built. People obtain feedback and inputs that can be incorporated in the next Sprint. 

Scrum puts emphasis on working product at the end of the Sprint that is really “complete” or “done”; in the case of software or IT product, this means code that is integrated, fully tested and potentially shippable or in position to be delivered. A major theme in Scrum is “inspect and adapt.” Since development inevitably involves innovation, learning, and surprises, Scrum emphasizes and focuses on taking a short step of development, inspecting both the resulting product and the efficacy of current practices, and thus adapting the product goals and process practices. Repeat forever (Jeff Sutherland, 2008).

Figure 6 Working of Scrum

Source: (Schwaber & Sutherland, 2010)

Ref - Software development company in india