170 likes | 406 Views
Visual Studio 11 ALM. Brian Harry Technical Fellow Microsoft. Visual Studio – Strong Track Record . Improving Application Lifecycle Management (ALM). 2005. Transparent Foundation. Developer <-> Architect Developer <-> Tester. Our Guiding Principles for ALM. Product Backlog. OPERATE.
E N D
Visual Studio 11 ALM Brian Harry Technical Fellow Microsoft
Visual Studio – Strong Track Record Improving Application Lifecycle Management (ALM) 2005 Transparent Foundation Developer <-> Architect Developer <-> Tester
Our Guiding Principles for ALM Product Backlog OPERATE DEVELOP Requirements Collaboration Actionable feedback Respect your work styles Sprint Monitor Stakeholder Feedback Transparent agile processes Ops Backlog Working Software
What Matters – Creating Value Product Backlog OPERATE DEVELOP Requirements Can’t Get ActionableFeedback MisunderstoodRequirements Idea to working software Incident to Resolution ConflictingPriorities Can’t Reproduce Production Incident Can’t Identify Root Cause Sprint Monitor LosingFocus Ops Backlog Working Software
What Matters – Creating Value Product Backlog OPERATE DEVELOP Requirements Idea to working software Incident to Resolution Managing the Backlog Quickly Triage Incident Lightweight Requirements Actionable Feedback Sprint Monitor Sprint Planning & Tasks Connected Team Context Switching Ops Backlog Working Software
Visual Studio vNext ALM – Continuous Feedback 2005 Developer <-> Stakeholder Development <-> Operations Transparent Foundation Developer <-> Architect Developer <-> Tester Designer: Just shift waves to the left and add in the vNext wave following the format of the other two
“Bottom up” View • A Great Agile Experience • Developers are “Raving Fans” • Evolve to the Cloud • Continue to expand to smaller teams • Support Windows 8
Team Foundation Service • Team Foundation Server hosted on Windows Azure • A really easy way to get started • Currently in “Preview” • Get started with your invitation code: “almdays”
Why Cloud? • #1 support issue for TFS is setup/reconfiguration • A dramatically easier getting started experience • Easier cross geography/organization collaboration • Overall lower operations cost – economies of scale • Better targeted product evolution • Faster delivery cycle • Future capabilities will need public facing servers
TFS Preview Demo
Server Vs. Service Service Server 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
Qualities of Service Security Authentication via LiveID. ADFS and other schemes in the future Data encrypted on the wire with HTTPS Secure data storage in Windows Azure and SQL Azure Performance “I was surprised how snappy the UI and operations from Team Explorer felt.” “So far performance is on par with our on-prem TFS system.” “Working with distributed teams is fantastic!” Availability 99.9% availability target. 99.93% realized thus far Continuous monitoring from multiple locations around the world
How Do We Get There? Hybrid server & service Store all assets on-premises while hosting targeted projects in the cloud Facilitated through the Spring 2012 release of the TFS Integration Platform Full-on Team Foundation Service Today: start fresh on the service Soon: copy on-premises data to the cloud via the Spring 2012 Release of the TFS Integration Platform Future: import on-premises team project collections to the cloud
Summary Collaboration Actionable feedback Respect your work styles Transparent agile processes
Team Foundation Service • http://tfspreview.com • Registration code: RduCodeCamp • Read my blog: http://blogs.msdn.com/bharry