A Lap Around Visual Studio 2012 ALM
•Download as PPTX, PDF•
0 likes•1,161 views
Solving the ALM Puzzle using the Microsoft suite of tools! My session at the #vbug user group in Bristol, UK. Make sure you check out the vBug website for more details. http://cms.vbug.net/Home.aspx
Recommended
Recommended
More Related Content
Recently uploaded
Recently uploaded (20)
Featured
Featured (20)
A Lap Around Visual Studio 2012 ALM
- 1. VBUG Talks in Bristol Coordinator David Ringsell david@talk-it.biz www.talk-it.biz Tweet @DavidRingsell
- 2. Free .Net & SQL Server Tutorials web and windows development programming in VB and C# database development object orientation http://talk-it.biz/category/tutorials
- 3. A Lap Around Visual Studio 2012 • Tarun Arora - Wednesday January 16th Entity Framework • Geff Lombardi Wednesday February 20th TBC Windows Azure Applications • Richard Conway Wednesday March 13th SQL 2012 New Features • Neil Hambly - Wednesday May 15th
- 4. A Lap around Visual Studio 2012! Tarun Arora [Microsoft MVP, ALM 4 Ranger]
- 5. Cmd/> WhoAmI
- 6. The ALM Puzzle! WORKING SOFTWARE
- 10. Impediments
- 11. Without barriers
- 12. Impediments
- 13. Without barriers
- 14. Impediments
- 15. Without barriers
- 17. Team Foundation Server Team Foundation Service SCM and Version Control Agile Planning & Collaboration Tools Feedback Requests & Issue Tracking Continuous Integration Builds Federated Identity Management Lab Management Detailed Reporting & Analytics On-Premises Server Integration
- 18. Next Steps www.visualstudio.com
Editor's Notes
- Tarun Arora is a passionate technologist working in Avanade, London. In his day job Tarun helps leading Energy Trading and Financial companies develop and support efficient, scalable and robust enterprise applications. His specialisms include Application Lifecycle Management (ALM) with Microsoft development tools with a strong expertise in implementing & leading Waterfall and Agile based development processes supporting distributed teams on large-scale .NET based enterprise projects. Tarun is a Microsoft MVP and a Visual Studio ALM Ranger. Outside of work he is found moderating MSDN forums, blogging and writing for MSDN, TechNet, Codeproject and other technology focused websites. For latest and greatest follow him on @arora_tarun
- This slide really sums up the software development lifecycle of an evolving application. Any given application will have a group that defines the road map for the application, this group usually consists of application users and stakeholders. This group is responsible for proposing & managing the product backlog for the application. This group is also responsible for defining the priorities on what gets done when. Then there is a team that manages the development & testing of the application. Lets call this the implementation team. This team turns the idea into working software. The implementation team churns ideas into working software, operations team has the onus to ensure the high availability & smooth running of these applications deployed in production. As issues are reported, the operations team collaborates with the end users to define the priority and accordingly get work added to the product backlog for implementation. Software should be viewed as a living asset, with the Application Lifecycle representing a continuum across the connected activities of a products lifetime, spanning: the identification of business needs, software construction, release management and monitoring, support and maintenance, through to the eventual retirement of the solution. Two flows are critical across the lifecycle, which span multiple teams, roles and individuals:Concept to working systems – shortening time to value, andDiscovery of an issue to resolution – lowering mean time to resolutionAn Application Lifecycle Management toolset must support these flows and accelerate the transitions between the development team and the operations team. As new requirements are established, applications evolve. There is a tight connection between the development and operations team, so whenever hand-offs exist there is a potential for bottlenecks to occur.