I just started a new series of videos where I show how to use Visual Studio to quickly take an idea into a real app and how to keep your project on track using the ALM features of Visual Studio Online.
This first part is about storyboarding the app, picturing a high level overview of the app components and creating a team project in Visual Studio Online with a prioritized backlog of requirements.
In the next video we’ll dive into the Kanban board and how to plan the first sprint.
In the last part of the series I show how to track the progress of your team using the new SharePoint Dashboards and the SQL Server Reporting Services that are part of the Team Foundation Server 2010 installation.
I hope this video series was of any help to anybody interested in learning about Visual Studio 2010, TFS 2010 and Team Build 2010. The series end here mostly because I have already shown most of what I wanted to show and also because Visual Studio 2010 RC is around the corner and I don’t want to mix stuff of Beta 2 with RC.
If there’s anything you’d like to see (or not to see anymore) on this blog please let me know, feedback is greatly appreciated!
In part 10 I show how to use Team Build 2010 to prepare a Continuous Integration build definition for the BookStore application. Continuous integration is a best practice that makes sure that any time a developer checks-in some code a new build is triggered, allowing the team to quickly find broken builds and fix them early in the development process.
As a side note I just want to highlight that the WMV video that you can download from the above link has better quality than the Youtube video, mostly because of Youtube processing of the video which, for some reason, reduces quality and un-syncs the video from the audio. Download the video for the best quality.
In part 8 I create and execute a test case and also record a bug using Test and Lab Manager, which is part of the Visual Studio 2010 suite of products. You can see how to include a screenshot, a video and more relevant information from the test result into the bug, which will in turn be very useful information for the developer.
In part 7 I create the user interface for the Book Store application. I show how to create a Windows Presentation Foundation (WPF) application that can take advantage of the Visual Studio Data Sources window and Data Binding. Finally I check in the new project associating it with the developer task.
In part 6 I continue doing some Test Driven to actually make our unit test go to the green state. I also show some quick ADO.NET Entity Framework use and finally how to check-in your code to Team Foundation Server while associating that check-in with the developer task.
In part 5 I show how to start coding using some Test Driven Development. Ran a little bit out of time, so this part covers from the Visual Studio solution creation to running the unit test getting a fail result. Next part covers making the test pass.
In part 4 I show how to plan your iteration, also known as sprint. You can see how to specify the iteration duration, assign tasks to team members and check your iteration capacity to make sure the team will not commit to more tasks than they can actually complete.
In this third part I show how to add users to Team Projects. This requires granting access to domain users in Team Foundation Server, SharePoint and Reporting Services. An easy task but usually causes a little confusion when working with TFS for first time.