Because at Y Soft we believe that sharing is caring, we have decided to organize a public meetup and share information about our LeSS transformation. Our journey has started about a year and a half ago and is still on-going. We believe, though, that we’ve learned a few lessons (sometimes the hard way) and picked up a few tricks along the way. But let’s start at the very beginning…

In the past, our development teams operated as separate entities, each in charge of their own product component and accountable only for their own Sprint. Architects evaluated the workload, broke it down and assigned it to the appropriate teams. But it was the team managers—answering to our product managers—who were ultimately responsible for the delivery.

We believed that this system would maximize the effectiveness of the Research & Development (R&D) team. Our “Agile Product Delivery” was supposed to make us more efficient by keeping track of the state of a feature through a Jira checklist, while the feature would transition between R&D and the rest of the company. We’ve come a long way since then, during which we’ve abandoned our wishful thinking—“it’s our managers’ responsibility”—and picked up a more helpful approach: “We can push this product forward only when working together.”

We won’t lie, changing the mindset of 13 teams and nearly 100 engineers wasn’t easy. We prepared for months and started adopting LeSS only in January 2019. From that moment on, we’ve grappled with challenges, learned a lot, experienced successes and failures—all to become more effective, together.

If you missed our meetup and want to learn more, watch the recording.
Password: 5p#r=#4*




  1. I blog quite often and I really appreciate your information. This great article has really peaked my interest. I am going to bookmark your site and keep checking for new information about once a week. I opted in for your RSS feed too. Wallie Erich Elodea


Please enter your comment!
Please enter your name here