SCRUM is one of the most popular and effective agile methodologies.
SCRUM is not an acronym. The word SCRUM derives from Rugby and it involves the team as a unit moving the ball down-field in what would appear to be a chaotic fashion.
The SCRUM methodology can be seen as chaotic at first glance but there are roles and a process to follow which brings order to the chaos. 
The SCRUM process contains the following steps:
Vision
A Scrum project starts with a vision of the system to be developed. The product owner in accordance with the stakeholders is then responsible to create a list with the description and functionality of the product. The anticipated ROI (Return on Investment) will be specified and included in the planning. This list is called the “Product Backlog”.
Product Backlog
The Product Backlog is a list of functional and nonfunctional requirements that, when turned into functionality, will deliver this vision. The Product Backlog lists all the requirements which need to be implemented. The most important functions which will maximize the ROI immediately are at the top of the list and will be done first. The list can be fluid in nature which means that if the requirements change for the business the Product Backlog will be changed accordingly. Change is welcome and the team can react to this quickly in the next Sprint.
Sprint
The programming work is done in the Sprints. Sprints last thirty days and at the end a new feature or function is added to the product. Sprints start with a Sprint Planning Meeting where it will be determined which functions of the Product Backlog will be tackled in the next sprint. The team, the product owner and the SRUM master are present at this meeting. The meeting itself is split in two four hours parts. In the first part, the Product Backlog will be presented by the product owner and in the second part the functions for the next Sprint will be chosen. This results in the Sprint Backlog. In the Sprint Backlog are all the features which need to be implemented in the next sprint cycle. The SCRUM master uses burn-down charts to monitor the status of the Sprint. The chart is displayed so that all team members have access to it.
Daily SCRUM
The daily SCUM meeting is an important factor to keep all team members in the loop. Usually people are standing during the fifteen minutes meeting.
The team has to answer three basic questions:
- What have you done on this project since the last Daily Scrum meeting?
- What do you plan on doing on this project between now and the next Daily Scrum meeting?
- What impediments stand in the way of you meeting your commitments to this Sprint and this project?
By answering these questions all team members will be up to date with the progress of the project.
|