Primero Systems Blog

Scrum-Butt: 3 Fundamental Changes That Make Scrum Work

If you’ve been around software development in any capacity in the last decade, you’re at least familiar with the concepts and principles of Agile and Scrum. Whether or not you can strictly define either or accurately characterize each as a methodology, framework, recommendation list, etc., is a whole other story that we won’t bother to touch here.

In any regard though, if you’ve ever asked anybody the question “Do you do Scrum?”, the answer invariably begins with “Yes…buuuutttt”, followed by a list of where their implementation of Scrum differs from the most traditional sense. It happens so often, that I simply refer to it as Scrum-Butt. The following is our own version of Scrum-Butt as applied at my company, Primero Systems.

In Primero Systems, we love the principles of Agile Software Development…and who wouldn’t? It’s hard in most cases to find anything wrong with the 4 key values of agile as described in the ‘Manifesto for Agile Development’:

  • Individuals and Interactions over processes and tools
  • Working Software over comprehensive documentation
  • Customer Collaboration over contract negotiation
  • Responding to Change over following a plan

The items above in bold are always preferred over its counterpart to the right.

OK…so far so good!

Scrum then is the methodology that we’ve employed for almost a decade now to help us adhere to the principles of agile development as listed above. This of course, isn’t anything new or special, as Scrum seems to be the method de rigueur of modern software development teams. We’ve been using it extensively across dozens of projects, clients and team members over the years.

However, Scrum in its purest sense, hasn’t always served us as well as we would hope. There are some fundamental challenges built into it that we feel take us too far away from our over-arching priority which is to build great software as efficiently as possible.

Read the Full Article

Ⓒ 2019 Primero Systems Inc.