My intention is to blog each week about different agile methods. Last week, I dealt with XP and hope it provided readers with some new information. This week I will be analysing SCRUM .
Firstly, what is SCRUM? It is an agile method based on “multiple small teams in an intensive and interdependent manner” (Margaret Rouse, Feb. 2007). Each members role is essential to success. The product owner has the most power as it is he/she or sets the goals and also accepts responsibility for the success or failure of the project. A ‘scrum master’ is appointed in the initial stages of SCRUM. He or she could be described as the mediator between team members from the product owner. The scrum master ensures that the team are working efficiently and also, reports the progress to the product owner.
How does SCRUM operate? This method is based on real-world progress. It does not work on estimates. The process is broken up into iterations known as ‘sprints’. These sprints take a maximum of 4 weeks. Team members have daily meetings. At the end of the sprint, another meeting is held and progress is analysed. From that, the next step is planned. It is like a manufacturing plant having numerous quality control stations. The second or third sprint and not pre planned. How they are approached depends on the success of sprint one. This allows SCRUM to be adaptive and that is why it is a popular method of software development.
Here is an image of the SCRUM process: