Skip to main content

[More Conferences]

Agile Testing Days 2014

I attended Agile Testing Days 2014 to perform the closing Keynote, a tutorial and was one of the Team in the Black Ops Testing Workshop


Agile Testing Days 2014

At Agile Testing Days 2014 I presented a keynote, a full day tutorial and a double track workshop session:

  1. Keynote: Helping Testers Add Value to Agile Projects
  2. Tutorial: Technical Testing in an Agile Environment
  3. Workshop: Black Ops Testing

Keynote: Helping Testers Add Value to Agile Projects

I presented the closing keynote to the conference.

Every Agile project is different, we know this, we don't do things 'by the book' on Agile projects. We learn, we interact, we change, we write the book we go along. Throughout all of this, testing needs to remain viable, and it needs to add value. Remaining viable in this kind of environment can be hard.

Fortunately, we can learn to add value. In this keynote, Alan will describe some of the approaches and models he has used to help testing remain viable. Helping testers analyze the 'system of development' so the test approach can target process risks. Helping testers harness their own unique skills and approaches. The attitudes that the testing process often needs to have driving it, and the skill sets that teams need to ensure are applied to their testing.

At a simple level, this is just Systems Thinking and Modeling. In practice this can prove highly subversive and deliberately provocative. Because we're not talking about 'fitting in', we're talking about survival.

I uploaded the slides to slideshare:

Watch the talk

The talk was recorded, the video has been released.

Watch on YouTube

Alan Richardson - "Helping Testers Add Value to Agile Projects" Keynote @ Agile Testing Days 2014 from Agile Testing Days on Vimeo.

Tutorial: Technical Testing in an Agile Environment

I have listed the blurb for this tutorial below:

Let's adopt the view that when we test on Agile projects we want to add value as often and quickly as possible.

On this tutorial we will use a mix of discussion, instruction, exercises and debriefs to explore what it means to work in an Agile Environment and how we can push our testing beyond user stories.

We will test an application together, and you will be challenged to add your unique value to the group. You will draw upon your experience as you test, share your thoughts and ideas, and learn nuances and new approaches from the group, and your own explorations.

Bring a laptop, or other electronic computing device which you think can use for testing, because you will be testing. Load it with whatever tools and resources you think you need. You can use them, and share them. We want to learn from each other and explore what it means to conduct Technical Testing in an Agile Environment.

Some stuff we will cover:

  • How to use Systems Thinking to test technically and understand the "System under development"
  • How to use System Thinking to understand the "System of development" and adjust your test approach accordingly
  • What does "Technical Testing" mean?
  • How far to push the boundaries of user stories
  • How to improve your technical skills
  • Technical Testing does not mean Automation
  • What are your existing "technical skills" - you probably have more than you think.
  • Risks and Issues with technical testing, and strategies to counter them
  • How to document and describe your technical testing to others

Because it was a tutorial, I have not made the slides available.

Workshop: Black Ops Testing

Tony Bruce, Steve Green, and myself hosted a double track workshop under our Black Ops Testing banner. Where we used redmine as the target application.

These workshops are fun to do, basically we go off and test an application, then we use that as prep for the workshop, figure out what we want to draw people's attention to, what we tested, how we made notes, what techniques and tools we used. Then we identify hints, tips and areas of people to target.

During the workshop, we have our plan for what we want to cover, but we also see what the people in the workshop do, we help 'pull' that out of the attendees in de-briefs so everyone can learn from each other. We also coach the attendees individually, or in groups, as they test.

The workshop feels very fluid and adhoc, but in reality, that's because we have done enough prep to allow it to flow.

Regardless, the attendees, and we, enjoy it.

I uploaded the slides to slideshare:

[List of Conference Talks]