Hi @Tom_Fought
It depends on the project.
I have worked on projects where we were 50 people on an AEM project. I have also worked on projects where were 10 or even less, 4.
Here I am talking about teams formed of pure AEM developers (considered backend), UI developers (considered frontend), test team (qa & automation), UX designers, scrum master(s)/iteration manager(s), Product Owners (PO), Business Analyst (BA), project manager, solution and/or enterprise architects.
There is not a predefined recipe like one-fits-all setup. Everything depends on the scope and budget. Depends on the type of the project as well, cause' you might have a PoC, or an MVP or a scale to Production solution. Also in different stages you may have different team sizes and roles. For example in a Discovery phase you might have only business people, end users, architect , BA and some senior technical people. Later you might reduce the number of architects and increase number of developers cause you want to deliver more and more. And later you might enter a maintenance phase where you downsize number of developers and increase L1 support people.
