Your request doesn't really make sense from a purist perspective. In Scrum teams a member doesn't get individual task assignments and team members don't individually move from one sprint to another. In Scrum a team works as a collaborative group, together working on the goal that was set for the sprint.
To achieve the goal during a sprint the whole team collaboratively creates a plan. This may involve backlog items and tasks. This is what TFS allows you to model. Individuals or even multiple developers then volunteer to do a task (some of the plan may have already selected ideal team members for the task, but that doesn't mean that person is solely responsible for it). This is also how TFS is used by scrum teams when using the Scrum process template.
As such the functionality you're asking for does not exist when using the Scrum template. When using the CMMI process template (optionally linked to Project Server) you can do these type of assignments. You can then also plan overall "releases" and you don't have to use "sprints".
So what you want is not possible. It's not possible because that's not how Scrum intends it.
What are your alternatives:
- You can ignore the way it's meant to be used and open the task board, filter by team member and see if there is any remaining work associated to that team member. There is no way to "move the team member" to a new sprint, but you could move additional work into the current sprint. Normally the Scrum team would see that it has additional time available during the Daily scrum and then work with the product owner to see what other PBI's they may be able to pick up in that sprint.
- Convert to CMMI, though I don't recommend it when you're planning to implement Scrum as it's intended. It's not an easy conversion and I suspect that most developers won't like it, but tools like WitMorph can be used to move your scrum template to the CMMI template to enable full project server integration.
- Hack the scrum template to support MsProject. I really don't recommend this, as it makes proper scrum adoption a lot harder.
Much better solutions would be to:
I personally recommend to experience the usage of the tools first-hand and in-person. But then again, I'm a scrum trainer myself and have had a lot of people in my classes who left with a firm grasp of how to apply the tools the way they're intended.