Resticting delivry to future Sprints

theju wrote:

How to restrict the delivery of change-sets targeted for future
sprints? For e.g., The project is currently at Sprint-1 and there are
WIs planned for Sprint-2. I don't want developers to deliver a
change-set that is associated with a WI planned for Sprint-2. How do
I do this?

By changing the project's process to enforce that a change set being
delivered must be associated with a work item that is planned for the
current iteration.

It would be good if you understand how process customizations work
rather than just blindly following these instructions. This is just
intended to help you find what you need to understand. This is what it
looks like for me; your mileage may vary.

From the RTC 2.0 Eclipse client: Open the project area. Process
Configuration tab > Team Configuration > Operation Behavior. In the
Operations table, find Source Control > Deliver (client), and click on
Everyone (default) column of that table. Check the "Preconditions and
follow-up actions are configured for this operation" box if necessary.
In the list of Preconditions, click on Descriptive Change Sets. On the
bottom right, for "Iteration work item is planned for:", select "must be
current iteration".