Skip to main content

What do I want? Everything to change! When do I want it? Yesterday!



 

It has been said have very little patience, which is mostly accurate. I think I can be both extremely patient and massively impatient across different issues of different magnitudes at different times.

That said I like to think I have gained a more considered perspective in the last year or so, particularly in relation to the issue of organisational change. During that process, I have noticed a trend in some of my interactions with others. 

Change, and the demand for it, is being used as a weapon. ‘If things don’t change around here then I’ll be on my way’ and ‘things would never change, so I gave up and left' are statements I’ve heard.

Even in my variably patient/impatient state my recent experiences have taught me that change is an ebb and flow process. The rate of change can be easy and fluid, or hard and unyielding, but never, ever, linear.

This rate of change versus the amount of patience is never more prevalent than when an organisation is in the process of agile transformation. Across various organisational levels, from directors to developers, patience is a rare commodity.


I believe the source of this trend of impatience is the innate human inability to see the bigger picture over longer periods of time. We simply struggle to see beyond our immediate situation, and the pain of change is often underestimated.


For example I have consulted on agile transformations in recent years, where my own and others frustration with progress grew over time. However when I look back I realised that the organisation had come from a state of:

  • Multiple projects in progress for each team, most of which never finished.
  • Uneven team skill sets; some with no test, analysis or deployment focused individuals at all.
  • No test automation or continuous integration/delivery.
  • Long, drawn out projects, which sapped morale and encouraged attrition.

To, in a relatively short space of time:
  • Each team worked on one project until it was done.
  • Each team had a blended skill set.
  • Almost every team had continuous integration and delivery integrated into their processes.
  • Testing individuals had 3 or 4 tools in their locker for testing at DB, Service and UI levels, plus an appreciation of the subtler arts of exploratory and context driven testing.

There were still issues to be resolved, but I know which the more desirable state for a working environment is. 

In short, when it comes to change, I find that many cannot see the wood for the trees. Next time you get frustrated, remember where you began and try look at the bigger picture.

Comments

Popular posts from this blog

Testers Guide to Myths of Unit Testing

One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively.

Also, I want to do a talk about it, so I figured I would test the premise, see if potential audiences were into it. I put this on Twitter:
Working on a talk about what testers might believe about unit #testing & how we interact with developers creating unit tests. Any challenges/additions for my list below? #development#agilepic.twitter.com/4oT5HE4qs3 — Ash Winter (@northern_tester) December 19, 201730 replies with ideas tends to indicate that people might be into it. 
The ListI thought, as my final blog of 2017, I would provide a super useful list of the myths and legends we as testers might believe about unit testing:
That developer…

Wheel of Testing Part 3 - Applications

I've only had to quit two jobs to finally find the time to finish this blog series. Winning at life. If you need reminders (like I did) check out Part 1 and Part 2 before reading on...

After the first two blogs regarding the Wheel of Testing, I was delighted to receive a few requests for the wheel itself, which got me thinking about applications of it, beyond what its original intent was, which I've explored in detail in part 1 of this series of intermittent blogs. Most models need a little air time to show their value, in software development we crank out models all the time, but I'm not sure how many get used. I am inspired by models such as the "Heuristic Test Strategy Model" by James Marcus Bach, as I have used it and seen the benefits it has brought for my clients, particularly the ability to ask questions. So, I wanted to create a model which has a number of use cases, both real and imagined:

Helping to unlocking a career in testing which may be stuck

It is no…

The Team Test for Testability

You know what I see quite a lot. Really long-winded test maturity models. 

You know what I love to see? Really fast, meaningful ways to build a picture of your teams current state and provoke a conversation about improvement. The excellent test improvement card game by Huib Schoots and Joep Schuurkes is a great example. I also really like 'The Joel Test' by Joel Spolsky, a number of questions you can answer yes or no to to gain insight into their effectiveness as a software development team.

I thought something like this for testability might an interesting experiment, so here goes:

If you ask the team to change their codebase do they react positively?Does each member of the team have access to the system source control?Does the team know which parts of the codebase are subject to the most change?Does the team collaborate regularly with teams that maintain their dependencies?Does the team have regular contact with the users of the system?Can you set your system into a given state…