You should use streams if your team is going to:
Adopt, or is already practicing, Agile software development practices.
Work in parallel on the same code for the same release.
Manage multiple parallel streams of development with a protected mainline.
Allow developers to easily branch and merge projects.
Enforce a single line of descent to prevent conflicts.
Make developers responsible for the impact of their changes on the rest of the application.
Use a copy, modify, merge methodology.
You should use projects if your team is going to:
Primarily manage non-software assets such as documentation and hardware assets.
Work in a regulated environment where it is necessary to pre-authorize each change before it is made.
Follow a traditional waterfall development methodology.
Use an SCC-based IDE for our development.
Use remote replication.
Related Topics