Workshops and Team Building –Skills Enhancement in a Fun Way

The details of the workshop are determined in consultation between Lemontree and the customer to achieve the desired effect goal. We have a number of different workshops, which can be adapted depending on the need. These workshops are not planned, but are ordered on a case-by-case basis.

The expert!

Time requirement: 2 hours
Preparations: none – come as you are!
The Lemontree expert Magnus Poromaa, with more than 20 years of experience in high-speed transactional system design solutions as well as extensive experience from commercial and custom developed solution platforms leads the dialogue in a fun, enthusiastic and interactive manner with the audience. He has been a core specialist in many big and known companies that have developed disruptive solutions changing how architecture is set-up.

He opens up for dialogue about architectural design choices, risk/rewards in design, possibilities with different design choices and gives the participants the possibility to challenge him in his forward manner to outline technical choices.

The technical level is widespread during the discussions to dig down into detailed technical matters as well as conceptual designs. No one leaves the room without having at least being challenged – or have had a good laugh while manoeuvring among all his experience condensed to a high-speed workshop. No one will leave the room without new knowledge or impressions and experiences from a long life building complex architectural platforms.

Suitable participants:

CTO, CDO, CIO, architects, DevOps/SRE & developers – and people that enjoy increasing their knowledge in architectural improvements in stable high speed transactional systems.

Buzzwords and key concepts:

We will browse through subjects and keywords such as Cloud solutions and management, different programming language applicability in different situations as well as buzzwords as cloud native, AWS, GigaSpaces, Digital Integration Hubs

The level of detail will be adjusted in the room depending on the knowledge level and interaction from the participants from high level concepts to coding standards and methods!

Hacking The Juice shop – Security Testing For Beginners

Time Required: 4 hours
Prerequisites: All participants need to have a software installed

Security testing is often perceived as something very difficult where only experts in the field can contribute. In this workshop it is demonstrated that there is much that can be done without having to be an expert in security testing.

In many of the teams we have worked with, security testing has been viewed as something that is purchased as an external service from an external vendor. After completed testing, reports must be reviewed which will lead to corrective measures. It is not uncommon for these types of reports to often show the same problems that occur repeatedly, but also that many of the errors highlighted are things that the team should be able to look for and find themselves. Instead of bringing in external help, you can get far with your own efforts and bring in the experts where it is really needed.

OWASP Juice Shop is a deliberately insecure web application that can be used for testing exercises at various levels of complexity. In the workshop, it is used as a lab environment to go through the top 10 OWASP risks. We will go through useful methods, tricks and tools to solve challenges in application security and how this can then be applied in real life. The focus will be on “low-hanging fruit”, i.e. things that can be done quickly and easily regardless of the situation in which the problems arise. Hopefully, you will be given many new ideas and a desire to learn more in the field.


  • You get new thoughts and ideas that can be incorporated into your everyday life with testing
  • You are introduced to security testing tools
  • You don’t need to be an expert to do security testing
  • A base in the field that can be used to advance you further in security testing

Agile Testing

Time Required: 1 hour preparatory meeting + 4 hour workshop
Prerequisites: None

Does your department, group or team have challenges with the transition to agile ways of working where traditional testing and hard boundaries between responsibilities no longer work? Do you feel that it is unclear to define roles and what are unnecessary bottlenecks and what are actually important processes, documents? and Do you want help defining your most important challenges, what is already working well today and get concrete tools to make the transition smoother? This workshop is for just that. We tailor it to your unique situation with a mix of concrete exercises, conversations and theory around agile testing, shift-left and the role of tester in an agile team.

For the best effect, we would like to start with a 1-hour conversation where the group that will participate in the workshop describes the current situation, challenges and their own expectations and wishes. Based on that, we produce material that goes through, for example:

  • Challenges – what are yours and what does the industry at large say?
  • Agile, shift left and continuous quality
    • How does it affect our role, our responsibilities and what we do?
    • What expectations do others have of us?
    • What expectations do we have of others?
    • Documentation – How do we document the right things in the right way?
  • Retrospective – What have we learned, what should we change and who is doing what?


  • Unified image of one’s own role and that of others
  • Unified picture of what is most important to change
  • Concrete areas of improvement

Test Driven Development (TDD) For The Curious

Time Required: 3- 4 hours
Prerequisites: You do not need to be a developer to benefit from this workshop. As a participant, however, you should have basic knowledge of modern software development and be comfortable with the idea of ​​writing code (with help from other participants).

In today’s increasingly agile world, digital solutions are produced like never before. When the long lead times in traditional waterfall projects are cut more and more, the ideal becomes to be able to deliver functionality and corrections as quickly as possible – ideally within a few minutes. But many times the solutions that are built are difficult to test and we get uncomfortable at the thought of changing something in that class that was written a few years ago by a consultant who changed assignments. The unit tests are few and only cover a fraction of the use cases. Sometimes tests are completely missing because there was “no time” and because the architecture makes it too complicated to write unit tests. Test Driven Development (TDD) is a methodology to deal with these problems.

When TDD is used successfully

  • the test drawing will be higher right from the start
  • you gain more confidence in your code and the changes you make
  • documentation (the tests) is produced and maintained on an ongoing basis
  • acceptance criteria are translated into code and can therefore be handled like any other code.

This workshop consists of a shorter theoretical part that explains how TDD came about and its elements. This is followed by a longer practical part where the participants collaborate to gradually deliver software to solve a fictitious problem. The group works in mob form, which means that one person at a time has control of the keyboard while another person tells them what to do. After a few minutes, the roles are rotated so that everyone participates.

The development platform consists of .NET Core, but since the entire group is helped on equal terms, it doesn’t matter if you don’t have previous experience with .NET.


An overall understanding of test-driven development and its levels.

Handy tricks and tips to bring into your everyday life.

Speed Testing With Mind Maps

Time required: 90 minutes – 4 hours
Prerequisites: Laptop and access to WiFi
Description: Are your test cases and implementations burdened by documentation and extensive processes? Do you think exploratory testing is too uncontrolled and desire more structured testing with formal reports? This workshop shows how to use visual models to increase the pace of testing without losing control.

In contrast to ad hoc or intuitive testing, exploratory testing assumes that testing experts have a structured approach to testing. Structure and processes tend to be perceived as obstacles in the speed of testing as time is limited and we need to shorten the implementation by “short cuts”. Taking short cuts creates a feeling of not being in control and also means that bugs can start to appear that are not noted in the testing. This need not be the case. You can learn to plan, test, adapt and report adequately with a minimum of time investment by using visual models. This “hands-on” exploratory test session will show how to use mind maps and techniques for planning, executing and reporting results. We will go through:

  • Requirements management (in fictitious business situations)
  • Planning, prioritisation and reprioritisation of tasks
  • Hands-on testing of a web application and how to draw conclusions from the testing
  • Adaptations due to the unpredictability
  • Summary and recommendations for continued work in a value-enhancing way.

The workshop is carried out in pairs or individually. No previous experience with mind-mapping is needed. Having worked with exploratory testing before can help but is not a prerequisite.


  • Knowledge of mind-mapping technology
  • Knowledge of how mind-mapping can increase efficiency and drive exploratory testing
  • Ideas and a template for planning smaller test executions

Risk Storming With TestSphere

Time Required: 60 minutes- 2 hours
Prerequisites: Laptop and access to WiFi
This entertaining workshop is carried out by playing a strategic board game together that focuses on identifying and finding test risks that affect the quality of your products. The workshop takes you through the different phases to answer questions such as:

  • Which quality aspects affect your product the most?
  • What risks can affect these quality aspects?
  • What should we do to minimise the risks from occurring?


  • You work as a team and can discuss appropriate testing strategies
  • You will develop proposals on how you can best focus on business value and risk
  • You will work with the TestSphere tool to identify unknown risks and strengthen your test strategy