4. Velocity and Quality Impediments
REQUIREMENTS
Misunderstood
requirements
Can’t get
actionable feedback
Conflicting
priorities
New learning's
Production incidents
• Loss of focus
• Integrating heterogeneous
development teams
• Quality after thought:
dev and test hand-offs Unmet user
expectations
Disparate management tools
Operations readiness WORKING SOFTWARE
requirements are not met
6. Unified ALM
SCRUM CMMI
TEAM
No-process FOUNDATION Custom
SERVER /
SERVICE
Testing Tools and Reporting and
Planning SCM Work Item Tracking Lab Management Build Automation
Services Analytics
23. Diagnostic Data Adapters
Video Capture System Info
Steps Performed IntelliTrace™
System Info
IntelliTrace™
24.
25.
26. Scaling Out TFS
TFS Cluster
Application Tiers Data Tiers
Team Project 1
Team Project 2
Team Project 3
Configuration
N Team Project 4
L
B Team Project 5
Team Project 6
Team Project 7
29. Modeling applications
• Visualize your code more quickly and easily.
• Read and edit dependency graphs more easily.
• Open and view linked model elements in work items.
• Generate C# code from UML class diagrams.
• Create UML class diagrams from existing code.
31. Developing applications and
collaborating more effectively as a
team
• Track tasks and boost productivity by using an
enhanced interface.
• Work more efficiently in a version-controlled
codebase.
• Conduct and track code reviews by using new tools.
• Perform unit testing by using a dedicated tool.
• Find duplicate code so that you can refactor
• Compare code versions by using an enhanced diff
tool.
• Work offline.
34. Automating and debugging builds
• Run, Monitor, and Manage Builds
• Define gated check-in build processes that support
multiple check-ins.
• Run native and third-party framework unit tests in
your build process.
• Debug your build process more easily.
• Finding Duplicate Code by using Code Clone
Detection
35. Server vs. Service
Server Service
Work Items, Source Control, & Build
Agile Product/Project Management
Test Case Management
Heterogeneous Development
Near-zero setup and administration
Collaborate with anyone, from anywhere
Virtual Test Lab Management
SharePoint Integration
Data Warehouse & Reporting
37. Recursos
TFS Branching and Merging Guide
http://vsarbranchingguide.codeplex.com/
Visual Studio Build Customization Guidance
http://vsarbuildguide.codeplex.com/
38. Text
Text
Text
Text
q w e r t y u i o p ⌫
a s d f g h j k l ‘ Enter
z x c v b n m , . ?
Ctrl &123 < > ⌨
Notes de l'éditeur
Agile practices do not equal the scrum model. It is about adopting the agile practices that work best for your organization.The cloud is not just about giving more benefits to users. Developers also benefit greatly from agile team tools to provisioning additional lab environments.Quality is a given for an app. Testing advances let you build quality into your application from requirements gathering all the way to completion.Developer roles are blurring and it is common for developers to perform the roles of operations, and vice versa.These trends have led to new ways to develop apps.
Speaker note: set the stage here for how continuous value delivery works. The next few slides go from a setup to the impediments that prevent it from happening, to how to address it.
Note : the ALM circle/loop visual is commonly misinterpreted as implying a SCRUM affinity. The intent of the circle/loop is not to imply a SCRUM or Agile (Agile with a Caps A) alliance. The intent of the circle/loop visual is to reflect a continuous evolution of software investments and the notion of continuous value delivery. The Define, Develop, and Operate lifecycle phases and the impediments that can surface within/across them are methodology agnostic. Team barriers and boundaries result in value delivery impediments that adversely impact the entire software lifecycle from requirements definition to production deployment & operations, and continuous evolution to sustain new and incremental value delivery. The net adverse impact is increased cycle time in delivering value to take the business forward at the needed velocity.Presenter TO DO : Select and drill down on an impediment in each of the lifecycle phases – Define, Develop, and Operate. Pick a mix of impediments that can be used to illustrate the following root causes : rigid processes (Ex : sequential/waterfall transition from development to testing)ineffective collaboration tools (Ex : lack of tools to enable continuous feedback loops with users, lack of integrations between tools used to manage development and operations workloads)development practices that do not take advantage of advances in technology and opportunities to better integrate dependent functions (Ex : not practicing acceptance test driven development, not using automated testing to validate business rules at the services layer, or DevOps practices to integrate development and operations teams in designing for operations and resolving production incidents)
Note : the ALM circle/loop visual is commonly misinterpreted as implying a SCRUM affinity. The intent of the circle/loop is not to imply a SCRUM or Agile (Agile with a Caps A) alliance. The intent of the circle/loop visual is to reflect a continuous evolution of software investments and the notion of continuous value delivery. The Define, Develop, and Operate lifecycle phases and the impediments that can surface within/across them are methodology agnostic. Team barriers and boundaries result in value delivery impediments that adversely impact the entire software lifecycle from requirements definition to production deployment & operations, and continuous evolution to sustain new and incremental value delivery. The net adverse impact is increased cycle time in delivering value to take the business forward at the needed velocity.Presenter TO DO : Select and drill down on an impediment in each of the lifecycle phases – Define, Develop, and Operate. Pick a mix of impediments that can be used to illustrate the following root causes : rigid processes (Ex : sequential/waterfall transition from development to testing)ineffective collaboration tools (Ex : lack of tools to enable continuous feedback loops with users, lack of integrations between tools used to manage development and operations workloads)development practices that do not take advantage of advances in technology and opportunities to better integrate dependent functions (Ex : not practicing acceptance test driven development, not using automated testing to validate business rules at the services layer, or DevOps practices to integrate development and operations teams in designing for operations and resolving production incidents)
This graphic was published by Gartner, Inc. as part of a larger research document and should be evaluated in the context of the entire document. The Gartner document is available upon request from Microsoft. *Gartner does not endorse any vendor, product or service depicted in its research publications, and does not advise technology users to select only those vendors with the highest ratings. Gartner research publications consist of the opinions of Gartner's research organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this research, including any warranties of merchantability or fitness for a particular purpose
Visual Studio Agents 2010 are set of technology—included with Visual Studio 2010—that enable tasks to be performed on behalf of one or more users. In the context of developer-tester collaboration, the most important Agent is the Test Agent, which includes a set of diagnostic data adapters, or DDA’s. There are several DDA’s which each server a different purpose. During test execution DDA’s can be used to:Collect a video capture of the tester’s machine.Collect the steps performed during the test execution.Collect system information from any or all of the machines involved in the test execution.Collect an action recording—a recording of the keyboard strokes and mouse clicks performed by the tester.Collect an IntelliTrace file which can be later used to replay the events that occurred during the test run.DDA’s can be used to impact the system under test (e.g. network emulation), and are extensible as well; so if there’s a piece of information which you find would be helpful for your developers to have from test runs, you can easily write your own DDA which collects that data for inclusion with the actionable bug.While this is not an exhaustive list of the DDA’s and their capabilities, these are the ones that will provide the most value when filing a bug; these are the DDA’s that will automate the collection of information that will turn a normal, somewhat helpful bug into a rich, actionable bug.
Preview ofevolved ETM architectureNew concepts introduced… will build back to this view to show how it impacts hosting in the EnterpriseLong term vision… several releases to fulfill promiseFocused in this discussion on investments for VSTS Codename: RosarioPlans may changeObjective…Manage Complexity, Achieve Agility - Reduce the TCO of deploying, managing, and customizing TFS as an enterprise-wide service so IT departments can focus on delivering new business value
http://msdn.microsoft.com/en-us/library/vstudio/dd409453.aspxGet an overview of your solution: On the Architecture menu, choose Generate Dependency Graph, For Solution.You get a graph that shows the top-level assemblies. You can now explore these assemblies by expanding them. Move the mouse pointer on top of an assembly, and then choose the chevron (^) button when it appears. Do the same for namespaces, types, and members to continue exploring your code.To see dependencies across groups, choose an item on the graph
