Why Scrum Software Development Rules

Why Scrum Software Development Rules

The waterfall method of development is as old as time itself.  For those unfamiliar, waterfall is a production process in which the development of a product takes place in sequential stages. It has served as a ubiquitous framework for production in various industries. Most notably, waterfall has been the go-to method for development teams in the software industry. In recent times however, time has caught up with the old waterfall process. This once popular software development process is losing substantial ground to more agile frameworks like Scrum. Where waterfall errors, Scrum thrives. Here's why.

One of the most common criticisms of waterfall is that the process allows for little flexibility. Developers are not able to make changes on the go. In today’s world, a lack of agility can cost a company time, money, and ultimately their business. This is why we at Intronis have bet our own business on Scrum.

Scrum in the Channel

Scrum is a framework that grew out of the Agile programming methodology and Object Oriented movement. Here’s how Scrum ultimately benefits managed service providers (MSPs), VARs – and their customers – out in the market.

Scrum is directly related to the principles laid down in the “Toyota Way” lean manufacturing process. You might ask yourself why and how a manufacturing process could be related to software development, and why Intronis -- which specializes in online backup and recovery -- would embrace Scrum to run our entire company. We’re about to answer all of those questions. And more.

One of the realities of software development is that requirements change. Sometimes requirements change faster than the project can be completed, and sometimes they change because what the customers thought they wanted was different from what they actually wanted.

How many times have you walked into an ice cream shop thinking “chocolate chocolate chip” and looked at the case and decided on the strawberry cheesecake? How many times have you used a piece of software and said to yourself “wow, this is nice, but wouldn’t it be great if it did this too?” Sometimes what you see just makes what you really want a little clearer.

Inflection Points

Sometimes the market changes too. New competitors surface all the time and old competitors are constantly changing and upgrading what they offer just as much as you do.

A company needs to be able to respond quickly and efficiently to changing customer needs and competitive pressure from others in terms of product offerings and cost if they want to survive.  Many legacy companies failed to do this. But here at Intronis, we believe we have found a solution to this problem: Scrum.

The whole idea behind Scrum is iteration and small steps that deliver real business value. So instead of focusing on the “Big Picture” while trying to implement the entire project with all items defined beforehand, Scrum starts with the truly American idea:
“How can I do the least amount of work and deliver the most value?”
Slyly, this doesn’t actually mean working less, it just means working RIGHT. We believe that, while thinking of the “Big Picture” is important, it isn’t as important as developing software that your customers really want and find it ridiculously easy to use. It follows that our customers -- MSPs, VARs and businesses -- will know what they want as they see it, and developing software is as much of a partnership with them as it is an engineering feat.

We believe that trying to do it all up front in the traditional waterfall method doesn’t work when your partners and customers are the focus, and the market is constantly changing. In order to get it right, you have to be agile in the true sense of the word, and Scrum provides the way to be truly agile.

mark-hatch-intronisMark Hatch is VP of software development at Intronis. Guest blog entries such as this one are contributed on a monthly basis as part of The VAR Guy’s 2009 sponsorship program.
Hide comments


  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.