I work for a company which is trying to understand how to scale Agile. We are an IT Service company, we don't work on one product, we develop many IT projects at the same time for our customers and we don't do body rental. We usually develop frontend (SPA, mobile apps) and backend (mostly Backend-For-Frontend).
Currently, when we obtain a new project from a customer, we set up a team specifically for that project. Then, we usually adopt Scrum or Kanban methodology to deliver that project and, at the end, we dismiss the team and we allocate those persons on other projects.
So our Agile adoption is based on single projects, it's not something done at organization level.
We start asking us if there's a better way manage things, considering that Agile assumes to create fixed, cross-functional teams that don't change also at the end of the project (if I've understood well), that should follow just one project at the time, but then we are struggling figuring how we could manage projects that, for example, requires just two Java developer or projects where we just need to develop the frontend, because the backend is delivered by another company or directly by the customer.
These are situations that I can't define "exceptions" as they are pretty normal in our environment.
Are we just looking the problem from a wrong perspective? What we should change?
Thanks a lot for your hints