“SCRUM”, is not a French word or the latest Scratch Back App but instead it is one of the smartest tool in our Magnificent11 BA Tool box.
Scrum is an Agile framework for completing complex projects. Scrum originally was formalized for software development projects, but it works well for any complex, innovative scope of work. The possibilities are endless. The Scrum framework is deceptively simple.
Use Scrum to improve teamwork, communications, and speed!
In this series, I will introduce you to the wonderful world of “SCRUM” by covering the basics, comparing it to the Waterfall development approach and show you the key fundamentals that makes “SCRUM” the favorite Agile methodology at Magnificent11.
In today’s post, we’ll focus on comparing the Waterfall development against Scrum Agile development. We need to understand the differences between Waterfall and Scrum which will highlight the benefits of Agile development.
The WATERFALL development
Waterfall is usually describe to be a long painful process from the first “Idea” all the way through “Development” or Building the software, this part is usually called “Planning”. Each step takes several months, the main problems is that Planning must take plan before any work can start and in most cases the planning is done without completely understanding or the project.
Most of the time, when there is a problem in the “development” process things have to be send back the “Idea” to go under additional planning. The same type of issue happens in the “Test” and deployment or “Final Product” process, this will ultimately create major delay such as many months or sometimes years before the product is out the door!
Considering the changing market, fast moving competition and new emerging and innovative start-up, you don’t have to be a genius to understand that your original “Idea” recorded 12 to 18 months ago will not stack up with the surrounding of “today’s world”.
SCRUM an Agile Methodology
Scrum is an Agile methodology which takes the process of development and breaks it down into smaller pieces call Sprint. Each sprint including the following process:
- PLAN: First will do just enough planning to get started.
- BUILD: Building the minimal feature set and actually build what was planned.
- TEST: Test the small feature set
- REVIEW: Review and potentially have shippable product
This process take about 2 to 3 weeks, this is then repeated time and time again reducing the time to development, to testing each time through the planning process so that we do just enough to complete the incremental releases. You will then end up with several incremental release call SPRINT, a Sprint usually take 1 to 3 weeks and you keep repeating these Sprints until your product is features complete. Sometimes is will take 3 Sprint or 4 Sprint or even more, but you eventually end up with a final product.
One of the key benefits of Scrum are the multiple touch points across each Sprint, there will always be an opportunity to adjust, adapt or make a change before a feature is complete. By the end of a project, containing for example 4 Sprint, you will have 4 opportunity to Plan, Build, Test, Review and the ability to modified a specific item without compromising the project.
Thank you for reading, I hope that it’s been informative and feel free to leave a comments below we would love to hear from you.
Next week we will focus on the 9 Key Component of SCRUM which are indispensable for the Scrum frame work to work well.