Application Lifecycle Management with Visual Studio 2010 Partner Briefing – March 2011Adrian DunneTechnical Solutions Professional | Microsoft Singapore
Agenda
ALM : A path with hidden pitfallsConceptLegacy CodeBroken BuildsReporting overhead“No-Repro” BugsPoor QualityPoor Estimation of cost and timePoor DocumentationIntegration IssuesNew Team MembersNo Shared VisionPoor UsabilityRealizationChanging architectureBuild QualityHeterogeneous EnvironmentScope CreepQuality concernsChanging Requirements
GovernanceImplementationOperationsThe 3 domains of ALM Idea is hereSolution is hereThe end is here
Team Foundation Server
VS2010 StackALM ReadyTest and Lab ManagerFunctional TestingLab managementIntelliTrace™ArchitectureUML Modeling
Layer Diagram
Dependency Diag.

ALM with TFS 2010

Editor's Notes

  • #4 Transition : One more pain point, and thisis not the least : the developer perception from Business leads and Testers!