Understanding development projects (and the database)

To improve the focus of our development work we'd like to better understand yours. In this two-page survey, please tell us to the best of your knowledge how you organize your database development teams.
1.How many projects will a typical developer work on in a 12-month period?
2.How many projects will a typical developer be contributing changes to simultaenously?
For a typical development project
3.What size is your development team working on the project?
4.How many in the team contribute database changes to the project?
5.How many development databases do you have for the project? (excluding those in the deployment pipeline)
6.Does each developer have their own dedicated development database?
7.How do developers mostly connect to the development database?
8.Excluding development databases, how many databases are in your deployment pipeline for the project? (eg. the answer would be 4 for 2 x Test + 1 x Staging + 1 Production)
More generally
9.In your organization, have you automated your deployment pipelines?
10.How many schemas are in the database(s) that you're typically working on? (an approximate number or guess is sufficient)
Privacy & Cookie Notice