Action Start on a project Home page in Web Access. Dialogue In this short video we want to demonstrate for you the new agile project management features that ship with Team Foundation Server. Our starting point is the project home page. This page shows some basic overview data for our project, including progress on our current iteration. It also displays summary information for the project as tiles at the bottom of the screen. Let's get started. Our first stop is the product backlog. Action Click on the "view backlog" link from the home page. Dialogue The product backlog is where we prioritize and organize what we want to work on next. Prioritization on the backlog is simple. We do this by dragging and dropping items on the backlog. Action Click an item from the top of top of the backlog and move it down, click another and move it up. Dialogue We can also quickly and easily assign a backlog item to an upcoming iteration, or open a backlog item to dig into the details. Action Move a backlog item to one of the upcoming sprints. Dialogue To add a new item onto the backlog we simply turn on the add panel, and enter a title for the new backlog item. Action Click the add panel on and add a new item. Dialogue Notice that items are added at the current location on the backlog. If we need to reprioritize, it's simple. In the interest of time, let's jump over and see an iteration that's already in progress – Sprint 1. Action Click on sprint 1. Dialogue TFS knows that this is the current iteration because each iteration in the system has a start and end date associated with it. The system also tracks progress on the current iteration with an up to date burndown chart. Action Highlight the burndown chart at the top of the page. Dialogue As you can see, the planning view provides some nice capacity planning views to help our team plan and load balance our work. The capacity is determined by the amount entered for each team member. Action Click the capacity tab and show the team members and hours. Dialogue Any changes made here are immediately reflected in the capacity bars on the page. Action Click back to the contents view. Dialogue To add new tasks, simple click the + icon below an item and complete the details of the task. Action Add a task including hours. Dialogue Notice again that when we added a new task our capacity bars immediately adjusted to give us a clear view of the work planned for the iteration. Let's now fast forward and look at the execution of the work for this iteration. To do this, we'll jump over to the board. Action Click the board hub from the top. Dialogue Here we see the same list of work for the sprint, only it's displayed visually as a task board. Each card on the screen represents work for someone on the team. We can quickly filter the list to see only our work, and we can drag things from state to state as necessary. Action Change the person filter. Move an item from left to right on the taskboard. Dialogue Our burndown chart is clearly visible for the team to track progress, and updates are reflected in real-time as changes are made. Action Reassign a task and update hours. Dialogue Finally, all the work shown here on the board shows up directly in your My Work pane in Visual Studio making it easy to associate your changes with the tasks you're working on. Action Switch to Visual Studio 2012 and show the tasks in My Work.
Action In Visual Studio, Create a new project, choose Coded UI Test Project. Dialogue Automated User Interface testing is ...
Action Look at the project references for a given project and then look at the next one. Dialogue Suppose your team has had ...
Action On My Work page, we see there are some file changes and an active task. Clicks the changes to go to Pending Changes, ...
Action Show solution with 2 files open in side by side mode in the editor. As the dialog progresses draw a highlight box ...
Action Start on a project Home page in Web Access. Dialogue In this short video we want to demonstrate for you the new agile ...
Action Starting with an "override" method, request Find All references. We get methods with the same name in many classes, ...
Activate if the team project does not have reporting enabled and the project was created using the @MSFAgileTemplateName@ ...
Activate if the team project does not have reporting enabled and the project was created using the @MSFCMMITemplateName@ ...
Activate if the team project does not have reporting enabled and the project was created using the @ScrumTemplateName@ process ...