Tag: TPI

Do not become a bottleneck for the agile project

Last November, during the EuroSTAR conference, I was asked to give a soapbox speech in the grand hall. During this “lightning strikes the keynotes” session I stated that if we testers don’t make haste with our test improvements we’ll become the agile project’s bottleneck.

I made a short summary of my arguments in the video below. In my latest edition of G(r)ood Testing 19: Let’s make haste with our test improvements I repeat this message, and also indicate some items that require attention in many organisations. You can read the column and my other columns in the series on the EuroSTAR community pages.

 

G(r)ood testing 13: The Context is Us

Test Process improvements are driven by the context. In our search for the optimal test approach, we assess the systems, the development methodology or the risks that we cover. However, there is a much bigger factor that we often overlook. This factor has a great influence on how we improve and what we improve.

Want to know what this factor is? Have a look at the introduction video (52 seconds) or better still: read the column for more details.

Implementing Test Automation, a story about changing insights and experiences

Today I gave a presentation on the Test Automation day. In this presentation I explain a simple strategy for implementing Test Automation in your organization. A simple strategy? I tell the story of my experience so far and look back in retrospective to the presentations I gave at the Test Automation Day before.
In this presentation I state that:

  • Organizational Maturity (like measured with TPI or TMMi) should not raise a threshold for getting started
  • In order to become good in Test Automation, we need to get started and learn from our mistakes (fail forward)
  • There is a shift from technology and tool selection toward selling the business case
  • But the real implementation is a process of organizational change, where people, and budgets play a key role.
  • People need to learn their new roles, need to work with new processes and you need to have a good story if you want to interfere with projects.
  • In the end, I conclude that once you completed the journey, and got the organization to start with test automation, you end up with the technical challenges again: What tool are you going to use, what architecture, and how do you write effective scripts….

A simple strategy? I am still learning.

 

 

The above presentation was preceded by a presentation from Ard Kramer. Today he gave this presentation alone, previously we gave this presentation together at the Dutch testing conference. The topics are very much related and its slides can be found here:

 

Discontinuity of test improvements !?

Testnieuws.nl published my column “The discontinuity of test improvements”. In this column I raise the question whether we are wrong in assuming that test process improvement  is a continue process.  The way in which you work towards the higher maturity from a natural growth, seems difficult and long. There is a faster way, but this way forces us to let go of some of the familiar principles. Maybe we should we accept that some of our truths, actually are outdated dogmas.  Bridge the gap between the old and new approach for TPI by reading my column…