A Report On The Scrum - 802 Words

This report is to discuss about the SCRUM (also known as Iterative Development Model), one of the famous software development methodology besides the Waterfall method. Introduction SCRUM is a model that emphasizes on breaking down projects into bite size portions therefore they are easily implemented and are aimed to be decommissioned quickly to cater their clients needs. A SCRUM team is responsible for the entire process of this development methodology which includes a product owner , scrum master and also chickens and pigs . The first step involves having to pick out a variety of tasks from the product backlog required by product owners / clients to form sprints. Sprints are similar to short duration goals that are†¦show more content†¦Clients have the freedom to change requirements for the project and also have access to the final products quicker. A minor bug in the Waterfall process will need to be re-written all over again from scratch. SCRUM is more flexible. When an error arises, changes can be made without having to repeat the whole entire process that incurs time and money .This is because the process or steps are done in several different sprints that are not immensely dependent on each other unlike the process that happens within the Waterfall methodology. Next, daily SCRUM meetings allow team members to come together to discuss the progress and roadblocks of the projects. There is transparency throughout the project development process. This gives them an opportunity to understand and help out each other if the need arises. Problems are identified in the early stages and resolved in a speedy manner. With this being said so, there is little bureaucracy and things get done more efficiently . Disadvantages of SCRUM There are a few reasons why SCRUM might not be the ideal method to be carried out. They are explained as below. The adaptability of SCRUM can also be a downfall for this methodology. If the product owner has no clear vision or being too ambitious for the project in the long run, the product backlog has a possibility of being filled with unnecessary tasks that will lead to an inefficient process as the team works with the requirements