Scrum is an iterative, incremental process for developing any product or managing any work. Scrum concentrates on how the team members should function in order to produce the system flexibility in a constantly changing environment. At the end of every iteration it produces a potential set of functionality.
The term ‘Scrum’ originated from a strategy in the game of rugby where it denotes “getting an out-of-play ball back into the game” with teamwork. Scrum does not require or provide any specific software development methods/practices to be used. Instead, it requires certain management practices and tools in different phases of Scrum to avoid the chaos by unpredictability and complexity
Key Scrum practices are discussed below
• Product Backlog – This is the prioritized list of all features and changes that have yet to be made to the system desired by multiple actors, such as customers, marketing and sales and project team.
• Sprints – Sprints are 30-days in length, it is the procedure of adapting to the changing environmental variables (requirements, time, resources, knowledge, technology etc) and must result in a potentially shippable increment of software.
• Sprint Planning meeting – Sprint planning meeting is first attended by the customers, users, management, Product owner and Scrum Team where a set of goals and functionality are decided on.
• Sprint Backlog – It is the list of features that is currently assigned to a particular Sprint. When all the features are completed a new iteration of the system is delivered.
• Daily Scrum – It is a daily meeting for approximately 15 minutes, which are organized to keep track of the progress of the Scrum Team and address any obstacles faced by the team.