HARTMANN software group

TFS 2017 Immersion Training in Berkeley

Enroll in or hire us to teach our TFS 2017 Immersion class in Berkeley, California by calling us @303.377.6176. Like all HSG classes, TFS 2017 Immersion may be offered either onsite or via instructor led virtual training. Consider looking at our public training schedule to see if it is scheduled: Public Training Classes
Provided there are enough attendees, TFS 2017 Immersion may be taught at one of our local training facilities.
We offer private customized training for groups of 3 or more attendees.

Course Description

 
This five-day immersion course is designed to get your entire team working efficiently with Microsoft's Application Lifecycle Management solution based around Visual Studio Team Foundation Server 2017 or Visual Studio Team Services. The course is divided into different topics on each of the days to help you gain a complete understanding of the features and capabilities of Visual Studio Team Foundation Server 2017. This class is designed for individuals or complete development teams who need to learn how to use Visual Studio 2017 and Team Foundation Server 2017 for Agile software development. This course covers team development, managing projects, Agile development, Agile testing, and DevOps.
Course Length: 5 Days
Course Tuition: $3390 (US)

Prerequisites

Attendees should be familiar with the needs of a software development team and the basic processes they would follow. Familiarity with Visual Studio and the basic use of Team Foundation Server or Visual Studio Team Services would be a benefit.

Course Outline

 
Module 1.1: Introducing Microsoft Visual Studio 2017 and TFS 2017
 
What’s new in Visual Studio 2017
Overview of the Visual Studio 2017 family
A lap around Visual Studio Team Services
 
 
Module 1.2: Organizing Work with Team Projects
 
Organizing projects in TFS or VSTS
Understanding process templates
Creating a new team project
Setting team project properties
 
 
Module 1.3: Managing Work Using Work Items
 
Overview of work items
Traceability between work items
Searching and creating custom queries
Work item charting and pinning charts
Work item tagging
Configuring project notifications
 
 
Module 1.4: Integrating the Team Using Different Clients
 
Using Team Explorer
Using Microsoft Excel to create and manage work items
Team Web Access
Third-party clients
 
 
Day Two: Managing Agile Projects
 
 
 
Module 2.1: Creating Our Product Backlog
 
Examining requirement types
Creating backlog items
Creating requirement hierarchies using features and epics
The importance of acceptance criteria
 
 
Module 2.2: Agile Estimation
 
Introduction to estimation
Using story points
Planning Poker and other popular estimation techniques
Adding your estimates to work items
 
 
Module 2.3: Working from the Product Backlog
 
Introducing the Kanban board
Entering and editing details on the Kanban board
Customizing columns including using split columns and limiting WIP
Recording our Definition of Done (DoD)
Understanding the Cumulative Flow Diagram
 
 
Module 2.4: Working in Sprints
 
Specifying your sprint schedule and team capacity
Selecting items for the sprint backlog using forecasting
Decomposing requirements into tasks
Using burndown charts to track progress
Monitoring work using the task board
Working with unparented work items
 
 
Module 2.5: Creating and Customizing Reports
 
Overview of reporting architecture
Reviewing the out-of-the-box reports
Adding new reports
Creating ad hoc reports using Excel
 
 
Day Three: Agile Development
 
 
 
Module 3.1: TFS Version Control Concepts
 
Version control in Visual Studio
Version control terminology
A closer look at workspaces
Changesets and shelvesets
 
 
Module 3.2: Using Team Foundation Version Control
 
The Source Control Explorer
Getting code into TFVC
Understanding the Pending Changes experience
Linking changesets to work items
Locking files in TFVC
 
 
Module 3.3: Configuring an Effective Version Control Environment
 
Working with workspaces
Setting team-project-wide source control settings
Check-in policies
Backward compatibility using the MSSCCI provider
 
 
Module 3.4: Branching and Merging
 
Defining a branching strategy
How to branch
Branch visualization and tracking changes
Merging and resolving conflicts
Custom differencing tools
 
 
Module 3.5: Unit Testing and Code Quality Tools
 
Unit testing in Visual Studio
Visual Studio Test Explorer
Code metrics
Static code analysis
 
 
Day Four: Agile Testing
 
 
 
Module 4.1: Creating Your First Test Plan
 
Creating a test plan
Creating test suites
Mapping requirements to tests
Mapping effort to specific builds
Configuring test settings including data collectors
 
 
Module 4.2: Authoring Test Cases
 
Creating and managing test cases
Creating reusable shared steps
Databinding our test cases
Using shared parameters
 
 
Module 4.3: Executing Test Cases
 
Assigning a test case to a tester
Navigating the Microsoft Test Runner
Recording reliable action recordings
Test Case Fast Forward
 
 
Module 4.4: Raising and Verifying Bugs
 
Raising a bug from the Microsoft Test Runner
Viewing bug states
Verifying a bug fix
 
 
Module 4.5: Exploratory Testing
 
What is exploratory testing?
Tools for exploratory testing
Creating bugs and test cases from exploratory tests
 
 
Day Five: DevOps
 
 
 
Module 5.1: An Overview of DevOps
 
Demystifying the DevOps buzzword
Understanding DevOps value
How the Microsoft stack supports DevOps
 
 
Module 5.2: Continuous Integration and Build Automation
 
Understanding the build infrastructure
Creating new build definitions
Configuring continuous integration
Build customization
Working with legacy XAML builds
 
 
Module 5.3: Release Management
 
Creating a release pipeline
Overview of deployment options
Configuring continuous deployment
Deploying applications to Azure
 
 
Module 5.4: Continuous Testing
 
Configuring automated testing
Web tests and load tests
 
 
Module 5.5: Monitoring Your Application Using Application Insights
 
Overview of Application Insights
Adding Application Insights to your web application
Tracking usage data
Viewing Application Insights data in the portal

Agile/Scrum Uses & Stats

Agile/Scrum is Used For:
Project Management Processes Maintenance Iteration
Difficulty
Popularity
Year Created
2001
Pros

Faster Deployment of Solutions
Because there is a continuous collaboration between stakeholders and teams, the focus on the essentials speed up the delivery process.

Gives Every Team Member a Purpose
People own and are expected to deliver on their responsibilities.

Keeps the End Goal in Mind at Every Level
With the end-goal in mind, teams stay focused and unite in their efforts

Promotes Flexibility in Order to Adapt
Close team and customer contact prompts acceptance of change, and frequent deliverables.

Faster Detection of Issues and Defects
Scrum methodology incorporates daily meetings, which helps to identify problems and resolving them in time.
 

Cons

Can Act As a Band-Aid to Bigger Problems
Agile has been the go to cure-method for larger issues that most of the time organizations are not able to deal with because they don’t have a neutral party to facilitate their corporate patterns, practices, policies and culture.

Can Create a Micro-Managed Environment
Practiced incorrectly, a project manager may not want to give up control and neutralize any real decision making from the team.

Not Everyone Is On Board
Although project teams may be ready for agile development, the rest of the company may not always be easily absorbed within larger more traditional organizations where there are significant amounts of rigidity or flexibility within processes, policies, or teams.

Push for Higher Performance
The push for a higher performance is even more relentless than in traditional, procedural organizations that have rigid processes or operating methods.

Not Well-Suited for Every Project
Agile may not work as intended if a customer is not clear on goals, the project manager or team is inexperienced, or if they do not function well under significant pressure.

Agile/Scrum Job Market
Average Salary
$89,553
Job Count
n/a
Top Job Locations

Agile and SCRUM methodologies are practiced mostly in larger organizations that have cross-platform teams that need to be on the same page. Adoption rates vary in different industries. 

 

Industry                       Agile Adoption Rate

Software (ISV)               23 percent

Financial services          14 percent

Professional services     12 percent

Insurance                        6 percent

Healthcare                      6 percent

Government                    5 percent

Telecoms                         4 percent

Transportation                 4 percent

Manufacturing                 4 percent

Complimentary Skills to have along with Agile/Scrum

Agile Methodologies and Frameworks include:

ASD - DevOps - DAD - DSDM - FDD - IID - Kanban - Lean - SD - LeSS - MDD - MSF - PSP - RAD - RUP - SAFe - Scrum SEMAT TSP UP XP

The Standards and Bodies of Knowledge Include:

BABOK - CMMI - IEEE standards - ISO 9001 - ISO/IEC standards - PMBOK - SWEBOK - ITIL

Interesting Reads Take a class with us and receive a book of your choosing for 50% off MSRP.