Skip to main content

Movie Quotes applied to Software Engineering... Nanny McPhee


The above quote as you can see is from Nanny McPhee, and it's as follows:

"When you need me but do not want me, then I must stay. When you want me, but no longer need me, then I have to go"

I think this applied very much to my role as a QA Lead, I seem to spend time with teams who need me, more than teams who don't. This isn't a bad thing, I know teams that don't need me will do fine without me, and by helping other teams I help improve them and improve their processes. I recently read a blog by James Bach here and I think this relates to the above, in that I jump (as James says, A Test Jumper) into help teams as and when I can and as and when it's needed, if teams don't necessarily need my help then I will spend less time with them. Every team is different and has different needs and different level of needs.

I've also said the above to an Agile Coach we had who blogs here, I often said to her that she's only around whilst we need her, and unfortunately once we didn't need her, she had to go, no matter how much we wanted her to stay.

Does this apply to your role? Or are you on the receiving end of this? Either way, feel free to comment, or comment if you don't agree! :)


Labels:

Comments

  1. Muhammad Hassan10 March 2018 at 09:22

    Excellent and very exciting site. Love to watch. Keep Rocking. Teknik Menggunakan File Lock PC - Avoid Hang Around Looking, Read through Concerning Cellular Desktop computers Within this article password protect folders xp

    ReplyDelete
  2. Muhammad Hassan18 March 2018 at 08:48

    Cant Play Videos In A Folder Lock On An PC - Don't Waste Time Looking, Study About Cellular Desktops Right here aharon

    ReplyDelete
  3. Kevin Dellinger23 January 2019 at 03:12

    Thank you, I've just been searching for info about this subject for ages and yours is the greatest I've discovered till now. But, what concerning the conclusion? Are you certain concerning the supply? Click here for info: The Ultimate Guide To Encryption Software & You Knew How To How To Encrypt A Password For Free But You Forgot. Here Is A Reminder

    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