Workspace and Schema Guidance

Question

Hi - We're setting up Apex and want to plan out how to handle workspaces and schemas in advance. In previous settings, workspaces were set up by department with one schema. It started to get messy as more applications were built and development and production was all done in the same place.
I was thinking that users could have their own development workspaces all associated with a development schema. Future workspaces would be created for each new project associated with the development schema previously mentioned and then separate workspaces for the project each associated with test and production schemas separately.
I've read through related postings but hoped that someone might have comments/pros/cons this structure:
WUser1Dev => SDevelopment
(Continue for each individual developer using the same schema)
WProject1Dev => SDevelopment
WProject1Test => STest
WProject1Production => SProduction
(Continue for each individual Project using the same schemas)
where W = Workspace and S = Schema

Answer 1

Related thoughts here: Re: Workspace Guidance .
Also consider that a dev-test-prod model where each is a separate database and in which workspace IDs are identical in each database (for each named workspace) is a whole lot easier to manage in terms of promoting revised applications and especially application components than a model in which dev-test-prod are separate workspaces that simply separate groups of developers from one another but where the applications within each workspace have functional counterparts in the others.
Also, it is essential that applications that need to interact with one another at runtime, by sharing session state and certain authentication-related machinery must belong to a common workspace.
Scott