At the onset of any project implementation, the concerned team has to make a vital decision- “Which development methodology can be used?” This is a serious matter of discourse. If you are working on any methodology for the first time, a clear definition of the development methodology is required. The team members should follow this definition and all its mandates strictly. This is nothing but the best way to organize the working of software development of all sorts. Clearly note that is NOT just another technical approach or simply a style of project management. Going forward, you will often find these terms being used interchangeably, which is downright wrong!
But why are we discussing this?
Because it works just the same way for Scrum.
Even before we start using Scrum, we should learn a little bit about the background of the methodology and understand why Scrum?. Firstly, why it came into existence and what was the problem with the traditional methodologies?
One of the long-lived methodologies is the Waterfall model which had dominated software development up until recently. The primary limitation of this model is the wrong “assumption” that all the requirements are clearly understood at the beginning of the project.
Let us dig a little deeper.
The Waterfall model was formally introduced for the first time in the year 1970 by Winston W. Royce who wrote-
“I believe in this concept, but the implementation described above is risky and invites failure.”
Given below is a quick rundown of the potential drawbacks of the Waterfall model-
In reality, the Waterfall model represents the well-defined stages of software development, and each stage must be completed before the next stage can start and there should be no overlapping of the stages. There is also generally a gate between each stage; for example, specifications must be reviewed and approved by the stakeholder before the design phase gets started.
To overcome these drawbacks in the waterfall development model, we adopt Scrum.
Scrum is one of the most popular Agile methodologies evolving in all aspects. It is an adaptive, fast, flexible, incremental, iterative, and effective methodology that was designed to deliver outstanding values quickly throughout a project. Scrum is responsible to maintain transparency of communication throughout the continuous progress of a project.
The entire project is divided into smaller chunks in order to deliver some features to the testing teams before the end of the development cycle. With the Scrum approach, we can deliver small working software product after each interaction and feedback from the stakeholder to increase or change the project according to response. These are the core values of the Agile approach.
At last, the project isn't for us, it is for customers. So they should get what they truly need, and no customer recognizes what they need at the start of a project.
A perfect enabler for organizations, Scrum offers listless benefits to its users. The most important ones are discussed below-
It is important to note that Scrum not only serves the respective teams or just the developers but is also of immense benefit to the customers. In fact, it helps generate customer-facing products and solutions.
Some of the potential benefits using Scrum to the customers are as follows-
One of the many attributes of Scrum is the range benefits it offers to the organizations implementing the framework. Below is a rundown of the benefits using Scrum at an organizational level-
Scrum processes and methodologies benefit the development team manifold. Some of the potential benefits using Scrum are discussed below-
We already discussed the benefits using Scrum towards the team and customers. Those benefits are real and significant and they do deliver the desired output. But basic and essential benefits aside, Scrum can also drive high financial benefits for the organizations. This may even include Return on Investment benefits which form a huge part of any organization's decision to commit to budget and scope.
Let us have a quick look at the financial benefits offered by Scrum-
Very nicely written!
i want to know more as a scrum master
Why would you justify your phrase " the same holds true for a Scrum Master, who must understand the technical issues the team needs to address and the technologies the team will use to come up with end solutions." using the Scrum Guide? There's nowhere in the Scrum Guide saying that Scrum master must have technical knowledge, so I would like to understand what is the rationale /logic behind this phrase.
Okay thank you so much for the info and you have mentioned in the blog.
I am really happy to read this blog as I was stuck in this type of problem many times and your blog solves my problem in one go. I can't wait to see your next post soon.