Application Lifecycle Management with Visual Studio Online

Day 1: Overview and Project management

Overview of the Visual Studio ecosystem

• What are the challenges?
• Overview of the different editions of Visual Studio
• The building blocks and features of Visual Studio, Team Foundation Server & Visual Studio Online
• Role-based approach in Visual Studio Online

Visual Studio Online

Visual Studio Online is a server product intended as the collaboration hub for everyone on the development team, inluding project managers, testers, architects, developers and end-users.

• Team Projects
• Using a Methodology like MSF or SCRUM
• Choosing and customizing a development process
• Setting up your team project

Work Item Management

• What are work items? What do they contain?
• Linking work items
• Creating work items using Visual Studio and other tools
• Using work item queries

Project Management

• Creating a Product Backlog in team Foundation Server
• Performing top-Down planning using work items.
• Creating a sprint backlog
• The sprint burndown chart
• Project management using the Visual Studio Online
• Powerpoint storyboarding

Day 2: Integration and Testing

Team Build and Daily Integration

To build quality software, and to limit nasty integration problems at the end of the project, doing a daily build is long regarded as a best practice. Team Foundation Server makes building daily very easy through Team Build. You'll learn how to manage the build, do desktop builds, and how you can setup Team Build to work in a continuous integration environment. We'll also look at Gated checkin, which prevent's anyone from breaking the build. You'll then learn how to customize the build process to perform all your build steps including running unit tests, creating custom build actions, generating setup programs and deploying to staging servers.

• Using Daily Integration for building better software
• Creating and configuring a build
• Doing Continuous integration
• Never break a build again with Gated Checkin
• Keeping track of things with Build Management
• Create rich customized build processes with Workflow Foundation

Team Testers

The new Test center is now the central place for testers to run and analyze their tests. Record the steps to test your software, and re-run the tests automatically later.

• Put your web site through its paces with Web Testing
• See if your code scales with Load Testing
• Using the new test manager
• Create test environments to run your tests
• Minimize retesting using impact analysis

Team Architects

• Use-Case diagram
• Class Diagram
• Sequence diagrams
• Activity diagram
• Component diagram
• Dependency Graphs and Architecture Explorer
• Layer Diagrams

Day 3: Version Control and quality control

Using Version Control

Sources are probably the most important part in any software project and we need a way to keep track of all sources and all changes. Team Foundation Server has a mature source control system, also used internally at Microsoft, supporting branching, merging and everything else required. Team Foundation Server also has a way to check sources before they are checked-in through check-in policies, limiting the number of broken builds to a minimum.

• Version Control concepts in Team Foundation Server
• Adding files to Version Control
• Single Checkout and Multiple Checkout
• Branching and Merging to work on multiple versions
• Visualizing branches and changeset merges
• Shelving for all kinds of scenarios
• Controlling the quality of code through Check-In-Policies
• Source Control integration for project management and reporting
• Distributed Source Control with Git

Team Developers

Developing quality software is not easy. That is why Visual Studio comes with a range of tools to make building software better.

• Writing tested and maintainable code
• Doing static code analysis with FxCop
• Reporting on maintainability using the Code Metrics report
• Post mortem debugging using Intelli-Trace
• Using Unit Testing in Visual Studio through Test Driven Development
• Using Fakes to better test your code
• Performing Code Coverage to find untested code
• Finding bottlenecks in your code with the Profiler
• Using Test-impact analysis