Leading a Scrummy lifestyle: What's often overlooked

Leading a Scrummy lifestyle: What's often overlooked

In my series about using agile processes not just for software development but in everyday life,  Socialize VP of Engineering Jason Polites has offered up a guest post about what often gets overlooked in software development:

Nice post.  I think there are some very basic tenets relating to SCRUM, or agile in general, that tend to get overlooked though.  Actually.. throw out the word SCRUM for a second and just consider what the concept of agile development is saying.

Imagine a situation where Person A has to complete Task X.  It doesn't matter what you do or say before they start, Person A will ALWAYS take the same amount of time to complete Task X.  Whether you are operating a waterfall model, an agile model or some other crazy methodology.. Person A will take the same amount of time to complete Task X.  But what does this mean?

If we have an approach that says "we need X tasks completed by Y date", then we are effectively saying we can predict how long it will take to complete those tasks.  If there is one thing we know with certainty, is that we can guarantee that things will change, and that we can't predict the future.  So, amazingly,  this approach fails every time (amazing not because it fails, but because it's still being used and people still expect it to work).

The reality is that you can't have tasks AND time.. you can only have one.  The tasks will take as long as they take.  We might "think" we can affect this, or we can fool ourselves into believing that we CAN predict the future, but restating the previous, "Person A will always take the same amount of time".

So.. if we accept that we can only have one or the other, how to we effectively schedule anything?  Well fixed dates DO exist (they're on the Calendar ;) ) so we can easily fix a date, but we CAN'T decide on a fixed set of tasks to be completed by this date.  Where does that leave us?  Well logically if we can only have a certain sub-set of tasks completed by a fixed date, then we want to make sure the most important ones are completed by that date.

Enter SCRUM stage left.

SCRUM advocates that you have a prioritized list of "tasks" (stories) such that completion order matters, but completion time does not.  SCRUM also advocates that at every definable stage (sprint) there is a viable product.  It may be featureless, but it "works".  There are a few assumptions here:

  1. We assume that people on the project and responsible adults, and that "Person A" (from the first example) will work diligently and efficiently
  2. We assume that the MVP (minimum value product) may need to more than one sprint to get going.  This is a bit of a deviation from the rules, but is a reasonable one.

Now although it's easier to see how this applies to software development vs. anything else, but actually in principle it applies everywhere.  It's just a way of looking at things and accepting that we can't predict the future.

You won't know what will be completed by a certain date, but you'll know that whatever is completed is the most important.