A stream is used to store the team's work. When you want to make your changes available to your team, you deliver them from a repository workspace to a stream. When you wish to incorporate other team members' changes, you accept them from the stream. Note that you can also accept changes directly from another repository workspace, allowing for fine-grained sharing of changes between team members. For example, two team members might collaborate on a small bug fix; or, if someone starts a change and has to go on vacation, another team member could continue the work and then deliver it later.

All changes you make in your repository workspace are tracked within change sets. Each change set is composed of a collection of explicit, primitive changes to one or more files or folders. A change set can also carry a comment and the reason the changes were made, typically by referencing the relevant work item. The source file base is built up from nothing but the steady accretion of change sets, each one building on everything that has come before it. Each repository workspace or stream is based on a sequence of change sets.
Let's start making changes and learn how these concepts can be used in day to day work.
You'll see a lot more for the Pending Changes view in the next sections, as it is really at the center of a developer's day-to-day work.
To check your project into Jazz Source Control:
To deliver the changes and make them available to the rest of the team: