How Visual Studio helps teams explore, understand, maintain, and uphold their project’s architecture. Introduction to some basic architecture & design concepts and common trouble spots for teams.
This post is part of a series of Visual Studio ALM webcasts that were delivered through 2010 and 2011 as part of an introduction to Visual Studio ALM. See An index to all Visual Studio 2010 Overview webcasts for a full list of webcasts.
Goals
- Visualize and investigate architecture with new VS diagrams
- Establish and enforce team standards
Demos
- Architecture Explorer
- Architecture verification
Recording
[screencast url=“http://www.screencast.com/t/ZvLy8P2Nlgwm" width=“640” height=“480”] Screencast: Visual Studio 2010 Overview – Introduction
This post is part of a series of Visual Studio ALM webcasts that were delivered through 2010 and 2011 as part of an introduction to Visual Studio ALM. See An index to all Visual Studio 2010 Overview webcasts for a full list of webcasts.
What to read next
Do you know about the Visual Studio 2010 Architecture Guidance?
Provides practical samples, checklists, and hands-on labs to help developers and architects use Visual Studio 2010 Ultimate’s architecture …
Visual Studio 2010 Overview - Code Management and Build
Explains branching, merging, and build strategies in Visual Studio 2010, including integration with Team Foundation Server and new tools for …
Visual Studio 2010 Overview Webcasts
Series of webcasts providing high-level overviews of Visual Studio 2010 and Team Foundation Server features, including ALM, testing, code …
Visual Studio 2010 Overview - A day in the life of ... Plan, Code & Test
Explore how developers, testers, and managers use Visual Studio 2010 and TFS for planning, coding, testing, bug fixes, and sprint management …
Embracing Change: How Architectural Adaptation Fuels Software Development Success
Explores how adapting software architecture to changing demands drives long-term success, highlighting incremental change, team investment, …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Detecting agile theatre with real delivery signals
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …