Skip to main content

Testing/Agile and American Football - A comparison

When I was in university I played football, not the English type, although I had played that all my life, but the American kind, with "offense" and "defense"  and "special teams".  I played defense and special teams, and both of them had what is known as a playbook (as does offense). This playbook had a list of plays that we would run in different scenarios depending on what the situation was or how risks averse we felt.

 The NFL season kicks off soon (next weekend in fact), and with this in mind, I was thinking this morning about how this can be used in testing, how we can have a playbook of different tests almost  all depending on the situation that we as testers find ourselves.

Just like in football we find that if we just use one "play"  or one form of testing the likelihood of being successful is slim. We need to mix things up a bit and use a wide array of plays or testing techniques in order to score or stop the other team from scoring, or in our case find bugs and release bug free software.

Let me start with the build up to gameday, here we'd have chalkboards and discuss the opposition, I liken this phase to test planning. In the case of a QA we would examine the requirements or the application if we have anything, and come up with a game/test plan on how we are going to test the software.

Come gameday, or in the case of an agile team, sprint time, we try and execute the game plan or test plan as well as we can. Just like in football there may be some outside influences that change what we can run or do, for instance the opposition might actually be playing differently to how we expected, but we adapt and change. In QA world, we could liken this to requirements changing, we don't stick rigidly to our game/test plan as it may no longer be applicable. This is fine, we just work with what we have.

During the game when the offense are on the sideline we can catch up and let the coach know what's working, what the opposition are doing, if anyone has any injuries etc. We can liken this to scrum! Where we let the team know what we are doing, if we have anything stopping us from working effectively.

When we find a bug throughout testing it is effectively a field goal, it's not quite a touchdown.. Why not? you may ask, I prefer to think of a touchdown as a fixed bug, something that we found, and was fixed, for instance we could find a low priority bug, that the business don't want fixed for whatever reason, it's still good that we found it, so... FIELD GOAL! 
A field goal is akin to a bug that is found, but just happens to be a low priority and doesn't get fixed.
We all want to find the high priority bugs, but in some cases we have to take what
we can.

 Oh, but if the field goal gets blocked, then it's effectively the bug being rejected!

 But if we find a high priority bug.. And it gets fixed, TOUCHDOWN! I suppose you could argue that a low priority bug is a field goal and a high priority bug is a touchdown.... But I'm going to stick to my analogy for now!
A bug that gets fixed, is akin to a Touchdown! If it passes regression testing
it's almost like the PAT was good! :)
There will come times when we are pushed that bit further, and we really have to come through, this can be likened to a 4th and 1 in football. For those who don't understand the rules, 4th and 1 means effectively you have 1 shot to move the ball 1 yard, or else the other team take over... This is effectively come the end of the sprint, we need to pull together to finish testing, can we as a team (developers included) manage it? Sometimes we do, sometimes we don't, just like sometimes teams make 4th and 1,sometimes they don't. However it wouldn't be for want of trying or effort. This situation could also be likened to a Hail Mary, in that you throw everything you have for one last push, one last chance of scoring/developing everything.

Come the end of the game, the sprint is over, or the release has happened, whether you win or whether you lost, whether we reached our sprint goal or not, or whether it was a successful release or not, there will be positives to come out of it, and negatives, here we review the game film, or review the sprint in a retrospective. We discuss what worked well, what didn't work well and how we can improve on it. And hopefully be ready for the next game/sprint.

I guess you can apply testing methodologies, or even Agile methodologies to any type of sport, providing you have planning, and reviews after, what happens in between, would be the "game" the money maker almost, what drives people to do what they do, nobody can say that test planning is the most exciting thing, it's the game day that they care about, or at least, it is for me. Game day doesn't have to be testing a piece of software, it can be driving practices forward, or coming up with improved methods that help game day run more smoothly or even influence the game day in some way to help get your desired outcome. 

 Going forward I will extend this theme and list some Testing Techniques/Approaches that are almost like our "playbook".


Labels:

Comments

  1. Unknown3 September 2013 at 07:13

    This comment has been removed by the author.

    ReplyDelete
  2. Unknown14 April 2016 at 02:22

    This is a wonderful article, Given so much info in it, These type of articles keeps the users interest in the website, and keep on sharing more ... good luck. football gloves

    ReplyDelete

Post a Comment

Popular posts from this blog

Coding something simple.... or not! Taking a screenshot on error using Selenium WebDriver

I recently wrote a little function that takes a screenshot at the end of a test if it has errored. What sounded very simple at the start turned out to be quite a bit of work, and quite a few lines of code to handle certain scenarios! It's now over 50 lines of code! I'll start with what I had at the beginning, this was to simply take a screenshot in the working directory, we are using SpecFlow and Selenium to run the tests, so we are going to check if the ScenarioContext.Current.TestError isn't null, if it is, then using Selenium, take a screenshot (note the below code is a simplified version of what I had at the beginning). [AfterScenario]         public static void TakeScreenShotOnError()         {             if (ScenarioContext.Current.TestError == null) return;             var screenshotDriver = Driver as ITakesScreenshot;             if (screenshotD...
15 comments
Read more

How to manage resources within new teams?

Working where I work we are constantly spinning up new teams to take on new workloads as business come up with new demands and new features they want developed and tested. The problem with this is how do we ensure the work of the newly spun up team is of sufficient quality. One method is by taking people from other established teams and placing them on the new team. This works great for the new team, but unfortunately it will oftenl eave the established team lacking in a resource whilst they try and fill the gap left by the person who has left. We are seeing this often with our offshore teams, it can be damaging to the team structure and the teams velocity, but try as I might, I can't think of another way around it. It's far easier to take 1 person from a team that is established than it is to build a whole new team from scratch. At least by leaving the core of a team in place, you should be guaranteeing that the new team are aware of any coding standards or any QA standard...
Post a Comment
Read more

Considerations when creating automated tests

We recently released to a number of teams our automated regression pack that has been worked on over the past few months. This regression pack tests legacy code, but contains a large number of tests.  As a bit of background, a number of teams are working on new solutions whilst some are still working on legacy code. With this in mind we constructed an email with a list of guidelines when creating new tests that need to be added to this regression pack.  I figured that these can be quite broad so should apply for any organisation, so thought it would make an interesting blog post...  So here goes,  when creating automated tests, it's important to consider and adhere to the following: - Think about data . The tests need to retrieve or set the data they need without any manual intervention - This should help them be more robust and easier to run without manual intervention. - The tests need to be idempotent - By making it so that each test is standalone and does...
Post a Comment
Read more