Lucian Adrian Stroie

R/GA, Romania

Lucian started as a tester around 2005, and now, 10 years later he is still in testing & enjoying it! His testing experience covers various types of software, ranging from firmware and embedded to web-apps, from the server side to mobile apps, biased towards exploratory testing. Besides testing, he has also taken steps in the project management and agile practices areas, gathering useful experience and combining with the testing mindset.

Currently, Lucian work as a test lead in an award-winning digital agency, coordinating the local test team as well as supporting the technology department with his technical expertise. Beside this main activity lines, Lucian conduct agile training as a collaborator in a consultancy company. For the community, Lucian is a volunteer in the local agile and testing communities, supporting the events with either sponsorship that he lobby for as well as with presentations.

Topic: Cynefin and Test Planning – an Option for Choosing the Right Testing Approach

Testing is a complex activity, involving many decision points and multiple possible approaches to the same end goal, that of ensuring the most useful information is provided about the tested software. At the same time, nature is also complex, and an inspiration source for some very useful models, such as Cynefin. This sense-making and context determining model is quite popular in the agile practices world, and can also be a good candidate for testing.

Is test automation the best approach? Should automation alternatives be considered? Should I build or buy my testing solution? These are some of the questions that people involved in testing are facing many times, and that can be made easier to answer to with the help of the Cynefin framework. The proposed session is an example of using Cynefin to make sense of the testing context, thus helping to determine the most suitable approach for testing. At the same time, since Cynefin is not a static model, the session highlights how the testing context is or can be changed, updating accordingly the testing approach.

The aim of the session is to introduce attendees to the Cynefin framework, as a tool for both decision making as well as for building support for the decisions they need to push out in the organisation. A secondary goal of the session is to emphasise the fluidity of the testing process and how this needs to change and adapt throughout the product lifecycle.

Key takeaway:

  • Awareness of the context challenges for testing;
  • Introduction of the Cynefin framework;
  • Mapping testing strategies to Cynefin complexity domains;
  • An example for supporting the “no-automation” decision.