Being a member of a project team is knowing what you can work on, and where to deliver the work so that it can be
integrated and tested with the work done by others in the team. A project will typically have one shared work area, and
multiple private development areas. The private development workspace allows a developer to work on tasks in isolation.
A developer joins a project, and in doing so has access to particular work products, and an integration workspace. The
next step is for the developers to create a private development workspace and populate it with the contents of the
project baseline as a basis from which to proceed. The project baseline is created by the Configuration Manager in
setting up the project CM environment.
Within the development workspace, developers perform tasks to work on work products. The work order provides a
description for what a team member needs to do. They can share their work with others in the project team by delivering
the changed set of work products into the project's shared work area.
In the shared work area individual work is integrated with that of other team members. Periodically, a new baseline is
created in the shared work area that incorporates the delivered work.
Developers update their private development workspaces to include the set of versions represented by the new baseline.
Periodically, as the quality and stability of baselines improve, the promotion level attribute of the baselines is
changed to reflect the appropriate level of maturity. Example baseline attributes are built, tested or release; these
are determined as part of the project CM policies.