Exploratory Testing

Ensuring quality in dynamic projects

   agilesoftware testingtesting tips

Agility and user-centered product development are turning the framework conditions for software development upside down. The goal: to quickly understand what people want. And to develop only what is desired. With UCD and Scrum, waterfall approaches to projects have found easily implementable successors. And the testing?
 

 

Too many test cases render test projects immobile

Traditional test procedures struggle to adjust tests to a dynamic environment with changing risks. You want to understand changing requirements? Then too many test cases may hinder you:

After a few sprints, the test expert pushes a bow wave of predefined test cases in front of him or her at the end of the sprint. The procedure suffocates by its own weight.

Agility in testing? Not a chance. Test cases and user stories quickly diverge.

 

 

Deliver without delay - even after strategy changes

The new version of the Android operating system comes with modified design guidelines. Or: In the 7th sprint after the first customer feedback on the beta, product development changes the target for the digital product.

In both cases: test cases would have to be fully adjusted. That takes time, and no new functions can be delivered to the customer for that amount of time. A risk-based tested version of the app, on the other hand, gets to the customer almost as quickly as a new feature otherwise would.

 

Your focus: Securing the right thing

Exploratory testing procedures ensure flexibility for your project and keep reaction times short - even after many sprints. Instead of running after the mirage of "testing everything", we ask you: What is the most important function? What is the worst case?

From your answers we derive how to keep the quality of your product as high as possible.

You will gain clarity for your prioritization: Is it best to invest in new features? Or would you rather focus on updating and stabilizing existing functionalities?

 

 

Gathering knowledge from many

Become a part of the performance: We incorporate the knowledge and curiosity of many stakeholders in explorative methods.

With "horror headlines" the whole team goes on a search for the worst risks for the joint project. With collaborative testing methods we use the dynamics of the group: Individuals become bolder and start experimenting. This results in more creative solutions than if they were alone. In mob testing people share their knowledge and different approaches to a problem.

Your project in the spotlight

With explorative test methods you prepare your software testing for agile and user-centered projects. Discuss with us the best way to implement them in your project. Either in direct conversation or during one of our presentations. That way you will get to know us and our methods better.

You are welcome to network on Twitter if you want to have a constant exchange.  Sven Schirmer or Benjamin Heinrich look forward to your ping.

 

 

Would you like to find out more? We're here to help

Call Sven Schirmer in Munich on 0151 544 22 051

Call Benjamin Heinrich in Munich on 0151 544 22 264