0:0022:03

Shift Left in the SDLC (Software Development Life Cycle)

Laia López 22:03 2023

Wallapop cut definition bugs 55% after making quality the whole team's job

Developers at Wallapop once had a safety net: they knew a tester would check everything afterwards, so edge cases slipped and fixes arrived late and expensive. Frontend engineer Laia López and three Wallapop colleagues explain why they moved testing to the start of the cycle and turned QA into risk assessment and requirements work. What does each role actually do differently when quality stops belonging to one team?

See how product, QA and developers each change their daily work when testing shifts left

Watch on YouTube

In short

Laia López and her Wallapop colleagues Agustina Santos, Anna Ruiz and Rebecca Porras explain how they moved from a traditional, phase-based software development life cycle to a shift left approach where quality is owned by the whole team. They describe the problems that prompted the change, how product, QA and development roles each adapted, and the benefits and challenges they found.

“Developers had a safety net, an insurance plan, because they knew that a tester would review the implemented product afterwards.”
“We have stopped seeing testing as a stage and we are now seeing it as a series of interventions that can and should be applied during the whole software development lifecycle.”

What you will learn

  • Distinguish a traditional, phase-based testing stage from shift left testing as a series of interventions across the whole cycle.
  • Spot the warning signs that call for shift left: QA bottlenecks, late feedback, low automation coverage and quality owned by one role.
  • Plan how product, QA and developers each change their responsibilities, from three amigos requirement sessions to developers testing their own code.
  • Measure the effect of shift left by classifying bugs by root cause and tracking definition bugs over time.
  • Anticipate the main adoption risks, such as blurry role boundaries and teams that need time to leave their comfort zone.

Key takeaways from the speaker

  • Shift left mindset
  • experimentation culture
  • SDLC
  • analytics
  • software developing

Details

Level
Intermediate
Format
Panel
Technical depth
Introductory technical
For
Early career, Mid-career, Senior individual contributor
Length
22:03
Published
June 2023

Questions this talk answers

What is the shift left approach in software development?

It is an approach where quality and testing practices happen earlier in the development life cycle, in planning, design and build. Testing becomes a series of interventions across the cycle and quality is owned by the whole team rather than a single role.

Why did Wallapop decide to adopt shift left?

They faced waits, bottlenecks and dependencies because developers waited for QA before merging, feedback came late and automation coverage was low. They also wanted to release faster, run more experiments and stop treating QA as the only owner of quality.

How does the QA engineer's role change under shift left?

Manual validation of each feature drops, and QA engineers focus on acceptance criteria, test plans, strategic thinking, requirements definition and risk assessment before coding starts. Remaining manual testing is mostly exploratory, and they spend more time analyzing quality metrics.

What results did Wallapop see from shift left?

The team said bugs caused by a lack of definition fell by 55% compared with the previous year, based on its internal classification of bugs by root cause.

What are the downsides of shift left?

Role boundaries can become blurry, teams used to working in a specific role need time to adapt, and test documentation has to be more exhaustive because the whole team now performs it.

About this talk

We are a group of 4 engineers working at Wallapop and we would like to discuss how has been our journey in applying the Shift Left methodology in our daily basis.

We would like to cover different ways of delivering, such as feature launches, A/B tests, smoke tests, releases and how that affects all different roles involved in the process.

Topics

Related talks

Browse the library