Agile Test Scan

Status quo of your Agile test process?

• Do you ever have reservations about the quality of delivered software and the speed with which delivery is involved?
• Do you ever get (much) less functionality in your software than you expected with a certain budget?
• Would you like a second opinion on the test process of your ICT organization?
• Do you notice that your testers have difficulty with the transition to Agile working and Agile testing in particular?
• Do you need budget support to help your development teams perform better?
• Do you need concrete advice and a plan for the development of your teams or team members?
• Have you been working with the same test suppliers for years and would you like a fresh look?

 

Then you should contact us, we are the Dutch software testing champion for a reason. We put the Agile test standard on the market. And to answer the above questions, we have developed the Agile Test Scan™ with which we determine the status quo of your Agile testing process.

Depending on the purpose of the scan, we start with an investigation of the company, the culture, the processes, the teams and the people in the teams. We then issue an independent report on this that is in line with the purpose of the scan.

Our Agile Test Scan™ uses the Lean A3 model, a structured and proven methodology that guarantees that the bottom stone comes out. The approach consists of the following steps:

• Background research; how is the problem relevant to the organization as a whole and what are the root causes?
• Current situation; what is actually happening right now?
• Problem: where is the deviation from the standards or the expectation?
• Goal: what changes do you want to achieve and when?
• Theme: what is the specific focus for this scan?
• Analysis: which issues can prevent us from achieving our goal?
• Countermeasures: can we anticipate these target-threatening issues?
• Implementation: who‘s doing what and what needs to happen exactly?
• Effect confirmation: how can we monitor the effects of the countmeasures?
• Follow-up: what are the next steps. How can we share and maintain what we learned?

The duration of the Agile Test Scan is largely dependent on the size of the company and the stated aim. It can take up to 1 day to a couple of weeks.

To the overview