Yesterday was five of you, today you can fill a stadium with all of you! Lengthy, old-fashioned, and overly complicated processes across teams? Immeasurable/infinite roadmap with non-stop stakeholders requests? Legacy code with a mixture of patterns? Code smell? Limited code coverage? High crash rate? Highlander ticket on your board?

No problem! You are not alone.

Team and process scaling is not a simple and smooth job if it's not reached gradually by a step-by-step incremental path. Accelerating this process due to business needs can bring a lot of problems at different company levels creating bottlenecks between people. Colleagues in the same squad, between different squads or across different teams can stop work properly introducing delays or loops across the flow.

So, where to start? How we can analyze and judge processes? How do we create a 'list of priorities and tasks? How we can achieve a good result and how do we measure it? How we can speed up our process and make team scale and at the same time find improve our code base?

This talk will guide you on our experience of how we survived (or at least we try to) in this ecosystem, and how we reacted to starting to create a good working env. At the end of the talk, you will have a good MacGyver-knife framework to use in similar situations which will help to improve your (and your team's) manner of working.

"The best way to beat a problem is to make it work for you." - MacGyver

This talk is based on the experience of my last 3 jobs across 8 years of experience I had the possibility to work in different organizations and face different problems.

The short version is a (20ish) light talk which can be easily extended bringing more examples to a full talk (40ish). The perfect audience for this talk is a mix one: engineers, managers, and PMs (not very much tech knowledge is required here) because the topic of the talk is investigating different (software cycle) layers.