SlideShare a Scribd company logo

Integrated ALM using Microsoft 2012 Solutions

•
•
Anup Hariharan Nair
Anup Hariharan Nair

Integrated ALM using Microsoft technologies improves the overall development efficiency by up to 30%. All in One Solution provides the best overall value and utility versus point solutions because start-up and recurring costs are normally less, features are better integrated, and reporting is much more seamless and robust.

Related slideshows

Dev opsnirvana
Dev opsnirvanaDev opsnirvana
Dev opsnirvana
 
Team Foundation Server Process Templates For Effective Project Management
Team Foundation Server Process Templates For Effective Project ManagementTeam Foundation Server Process Templates For Effective Project Management
Team Foundation Server Process Templates For Effective Project Management
 
UX in ALM Series - UX Project Worflow using TFS 2008
UX in ALM Series - UX Project Worflow using TFS 2008UX in ALM Series - UX Project Worflow using TFS 2008
UX in ALM Series - UX Project Worflow using TFS 2008
 
1 of 33
Integrated Application Lifecycle Management (ALM) Using Microsoft 2012 Solutions Presentation By Anup Hariharan Nair Date: 20 July 2012 http://HiFiCoding.com/ Prepared using :
What is Application Lifecycle Management?  Application Lifecycle Management (ALM) is a proven set of tools and processes that helps organizations manage the entire lifespan of application development, reduce cycles times, and eliminate waste.  ALM integrates different teams, platforms, and activities, enabling a continuous flow of business value.
Point Solutions for ALM  Serena  Project Management, Change Management  Concurrent versioning system  Code versioning, Team Build, Work Item Tracking.  HP - QC + QTP  Manage Defects, Test Plans, Test Cases, Test Results and Automated Tests.  Spreadsheets and Documents  Excel, Word, Visio documents.
Limitations of Point Solutions  Serena  Tool for Project Management and not for the entire team which includes developer and testers.  HP Quality Center  Tool for Testers – Not for developer • Developers work on a different environment (Visual Studio) and don't want to use other tools that have no relation and connection to the Developer work.  Backtracking • Backtracking becomes difficult when team uses different tools for development and testing.  Point Solutions  Both Serena & Quality Center are Point solutions which do not address complete ALM.  Someone needs to sync between the Project Documents, Serena, TFS and HP Quality Center.  Syncing and referencing the information from 4 different tools increases the time in an application lifecycle by up to 30%.
Collaboration through Integration  The key for good Application Lifecycle Management is collaboration through Integration with team members and the tools they use to do their primary job.  Product Managers, Developers and Testers are part of the same Team and the same Process.  In order to improve product quality, they all need to work together and share information easily and quickly.  If we want to apply integration inside the team, then we all need to work with the unified tool.  This unified tool will help share information across the entire team.
All in One vs. Point solutions  All in One -  One platform for the entire team.  Synchronizing between different tools is no longer necessary as they all are a part of an integrated platform.  Collaboration and integration become easy and fluent, collecting data to generate reports no longer needs to take a lot of time.  Microsoft created Team Solution for each individual position on the team; there are tools for :  Requirement Management.  Design tools for Architects.  Developer tools.  Testing tools ranging from manual test to automation and load testing.
Microsoft’s Integrated ALM Integration - 30% increase in overall ALM efficiency.
Integrated ALM Advantages  All in One Solutions provide a number of advantages because of the fact that they are tightly integrated:  User Setup and Security  Project Setup  Traceability  Dashboards and Reporting  Ease of Use  Initial Costs  Maintenance Costs  Training Costs  Upgrade Costs  Professional Services Costs  Development Costs  Integration Costs  Reporting Costs
TFS - Project Management Audience – 1. Project Manager 2. Business Analysts 3. Team Leaders
TFS - Project Management  Team Foundation Server provides MSF for Agile, CMMI and SCRUM process templates; or you can choose from a number of third party process templates.  Microsoft Excel Agile Planning Workbook can be used to create and manage the product backlog, estimate the team’s velocity, and break the project down into iterations.  The Iteration Backlog enables to plan iterations and track progress. In addition, integration with Microsoft Project enables stakeholders and project managers to gain real-time insight into project health as well as ways to improve existing processes.
PM - MS Project 2010 Integration
New in TFS 2012  TFS 2012 removes the worksheets and adds these features to the Team Web Access web interface.  Each team project has its own web application for managing the work of a project.  This isn't the SharePoint portal from previous versions, which still exists in the new version, but a newly designed Web Access application.  From here, project managers can view and manage their project, administer iterations and work areas, manage team members, and access reports.
New in 2012. Microsoft Feedback Client  You can respond to a request for feedback using Microsoft Feedback Client, a tool that allows you to launch an application,  capture your interaction with it as video and capture your verbal or type-written comments as well.  Your feedback is stored in Visual Studio Team Foundation Server 2012 RC to support traceability.
Project Development Audience – 1. Developers
Team Foundation version control  Check-ins for a group of items or for single changes.  Branching and merging.  Shelving.  Check-in policies.
Developer - Create a Work Item
Developer - Code Check In
What's new in TFS 2012  Query launcher in Pending Changes –  People wanted an easier way to associate work items on check-in.  Microsoft added a Queries drop down to pending changes allowing you to launch a query and then drag & drop a work item into the associated work items list.
What's new in TFS 2012  For developers, TFS 2012 includes significant changes in Team Explorer that are geared toward making the development workflow more efficient.  The main change is in Team Explorer's UI.  Team Explorer 2010 and previous versions provided one window where everything resides (e.g., work items, reports, documents, builds).  These items were presented as treeview menu items that can be expanded and contracted by clicking them.  TFS 2012 Team Explorer has changed this to a more context-specific interface.
What's new in TFS 2012  Code reviews.  TFS 2012 now includes a fully integrated code review process  Example a developer suspends work to address a priority issue that affects production. When the issue is fixed, the developer wants a code review done prior to checking in the code.  On the TFS 2012 Team Explorer Home screen is a Request Code Review link. Clicking this link opens the New Code Review screen. From here, one or more reviewers can be assigned by either typing in the person's name or selecting it from the drop-down list. You can add a description to the review request.  When the request is submitted, it will show up as a code review request in the reviewer's My Work screen.
What's new in TFS 2012 Detect Changes to Files or solution folder
Microsoft Team Explorer Everywhere for TFS  IDE’s based on Eclipse 3.5 to 3.7 on Windows, Linux, Mac OS X, Solaris, AIX, or HP-UX.  Any of the following versions of the Java runtime:  Sun Java™ 1.5 to 6, or IBM Java™ 1.5 to 6 on Microsoft Windows  Apple Java™ 1.5 to 6 on Mac OS X  Sun Java™ 1.5 to 6 on Linux or Solaris  IBM Java™ 1.5 to 6 on Linux or AIX  HP Java™ 1.5 to 6 on HP-UX  Works with Visual Studio Team Foundation Server 2012 RC, Visual Studio Team Foundation Service Preview, Visual Studio Team Foundation Server 2010 or Visual Studio 2008 Team Foundation Server.
Microsoft Team Explorer Everywhere for TFS
Project Testing Audience - 1. Testers 2. QA Engineers 3. Developers
MS Test Manager  Define Testing Effort  Create and Run Manual Tests  Record Manual Test Steps for Playback  Create Automated UI Tests  Create Physical or Virtual Test Environments To Use To Deploy Your Application or Run Your Tests  Collect Diagnostic Data or Affect Your Test Machine and Easily Add Collected Data to a Bug  Group Your Automated Tests By Using Test Categories
Microsoft Test Manager
What’s new in Unit Testing  Smart Test Discovery  Previously, when a test project was built, Test Explorer would perform an exhaustive search to discover the tests. A Smart Test Discovery algorithm has been implemented that significantly improves the time required for updates to appear on the Test Explorer Window.  Run Tests After Build a.k.a Continuous Test Runner  When this feature is turned on, the tests are run automatically after every successful build. If there are failed tests from previous runs, they are executed first.
JavaScript Unit Tests on TFS with Chutzpah – Leverages VS 2012 – Build Summary. functionality to discover and run unit tests
HP QC to TFS Migration  Scrat  Scrat converts and migrates all of your HP Quality Center projects and items over to Microsoft Team Foundation Server 2010.  The migration is quick, easy and a safe process that completes in just a few hours.  Contrary to the manual migration traditionally employed by organizations, Scrat fully automates the process.
Scrat
Garter Positions Microsoft in ALM Leaders Quadrant  Gartner, a leading industry analyst firm, evaluated 16 vendors based on their completeness of vision and ability to execute in the Magic Quadrant for Application Lifecycle Management.  Complete report details available at http://www.gartner.com/techno logy/reprints.do?id=1- 1ASCXON&ct=120606&st=sb
Conclusion  Integrated ALM using Microsoft technologies improves the overall development efficiency by up to 30%.  All in One Solution provides the best overall value and utility versus point solutions because start-up and recurring costs are normally less, features are better integrated, and reporting is much more seamless and robust.
References 1. http://support.smartbear.com/resources/sp/All-in-One.pdf 2. http://www.codeproject.com/Articles/304883/The-Future-of- Testing-Quality-Center-vs-Team-Found 3. http://www.hp.com/hpinfo/newsroom/press_kits/2010/HPSoftwar eUniverseBarcelona2010/Whats_new_in_HP_Application.pdf 4. http://www.microsoft.com/visualstudio/en-us/products/2010- editions/team-foundation-server/features 5. http://go.microsoft.com/?linkid=9747928 6. http://msdn.microsoft.com/en-us/library/bb385832.aspx 7. http://www.devproconnections.com/content1/topic/tfs-2012- 143104/catpath/visual-studio-2011/page/2 8. http://www.microsoft.com/visualstudio/11/en- us/lifecycle/develop-test 9. http://blogs.msdn.com/b/bharry/archive/2012/05/31/visual-studio- tfs-2012-release-candidate-available-today.aspx

More Related Content

Integrated ALM using Microsoft 2012 Solutions

  • 1. Integrated Application Lifecycle Management (ALM) Using Microsoft 2012 Solutions Presentation By Anup Hariharan Nair Date: 20 July 2012 http://HiFiCoding.com/ Prepared using :
  • 2. What is Application Lifecycle Management?  Application Lifecycle Management (ALM) is a proven set of tools and processes that helps organizations manage the entire lifespan of application development, reduce cycles times, and eliminate waste.  ALM integrates different teams, platforms, and activities, enabling a continuous flow of business value.
  • 3. Point Solutions for ALM  Serena  Project Management, Change Management  Concurrent versioning system  Code versioning, Team Build, Work Item Tracking.  HP - QC + QTP  Manage Defects, Test Plans, Test Cases, Test Results and Automated Tests.  Spreadsheets and Documents  Excel, Word, Visio documents.
  • 4. Limitations of Point Solutions  Serena  Tool for Project Management and not for the entire team which includes developer and testers.  HP Quality Center  Tool for Testers – Not for developer • Developers work on a different environment (Visual Studio) and don't want to use other tools that have no relation and connection to the Developer work.  Backtracking • Backtracking becomes difficult when team uses different tools for development and testing.  Point Solutions  Both Serena & Quality Center are Point solutions which do not address complete ALM.  Someone needs to sync between the Project Documents, Serena, TFS and HP Quality Center.  Syncing and referencing the information from 4 different tools increases the time in an application lifecycle by up to 30%.
  • 5. Collaboration through Integration  The key for good Application Lifecycle Management is collaboration through Integration with team members and the tools they use to do their primary job.  Product Managers, Developers and Testers are part of the same Team and the same Process.  In order to improve product quality, they all need to work together and share information easily and quickly.  If we want to apply integration inside the team, then we all need to work with the unified tool.  This unified tool will help share information across the entire team.
  • 6. All in One vs. Point solutions  All in One -  One platform for the entire team.  Synchronizing between different tools is no longer necessary as they all are a part of an integrated platform.  Collaboration and integration become easy and fluent, collecting data to generate reports no longer needs to take a lot of time.  Microsoft created Team Solution for each individual position on the team; there are tools for :  Requirement Management.  Design tools for Architects.  Developer tools.  Testing tools ranging from manual test to automation and load testing.
  • 7. Microsoft’s Integrated ALM Integration - 30% increase in overall ALM efficiency.
  • 8. Integrated ALM Advantages  All in One Solutions provide a number of advantages because of the fact that they are tightly integrated:  User Setup and Security  Project Setup  Traceability  Dashboards and Reporting  Ease of Use  Initial Costs  Maintenance Costs  Training Costs  Upgrade Costs  Professional Services Costs  Development Costs  Integration Costs  Reporting Costs
  • 9. TFS - Project Management Audience – 1. Project Manager 2. Business Analysts 3. Team Leaders
  • 10. TFS - Project Management  Team Foundation Server provides MSF for Agile, CMMI and SCRUM process templates; or you can choose from a number of third party process templates.  Microsoft Excel Agile Planning Workbook can be used to create and manage the product backlog, estimate the team’s velocity, and break the project down into iterations.  The Iteration Backlog enables to plan iterations and track progress. In addition, integration with Microsoft Project enables stakeholders and project managers to gain real-time insight into project health as well as ways to improve existing processes.
  • 11. PM - MS Project 2010 Integration
  • 12. New in TFS 2012  TFS 2012 removes the worksheets and adds these features to the Team Web Access web interface.  Each team project has its own web application for managing the work of a project.  This isn't the SharePoint portal from previous versions, which still exists in the new version, but a newly designed Web Access application.  From here, project managers can view and manage their project, administer iterations and work areas, manage team members, and access reports.
  • 13. New in 2012. Microsoft Feedback Client  You can respond to a request for feedback using Microsoft Feedback Client, a tool that allows you to launch an application,  capture your interaction with it as video and capture your verbal or type-written comments as well.  Your feedback is stored in Visual Studio Team Foundation Server 2012 RC to support traceability.
  • 15. Team Foundation version control  Check-ins for a group of items or for single changes.  Branching and merging.  Shelving.  Check-in policies.
  • 16. Developer - Create a Work Item
  • 17. Developer - Code Check In
  • 18. What's new in TFS 2012  Query launcher in Pending Changes –  People wanted an easier way to associate work items on check-in.  Microsoft added a Queries drop down to pending changes allowing you to launch a query and then drag & drop a work item into the associated work items list.
  • 19. What's new in TFS 2012  For developers, TFS 2012 includes significant changes in Team Explorer that are geared toward making the development workflow more efficient.  The main change is in Team Explorer's UI.  Team Explorer 2010 and previous versions provided one window where everything resides (e.g., work items, reports, documents, builds).  These items were presented as treeview menu items that can be expanded and contracted by clicking them.  TFS 2012 Team Explorer has changed this to a more context-specific interface.
  • 20. What's new in TFS 2012  Code reviews.  TFS 2012 now includes a fully integrated code review process  Example a developer suspends work to address a priority issue that affects production. When the issue is fixed, the developer wants a code review done prior to checking in the code.  On the TFS 2012 Team Explorer Home screen is a Request Code Review link. Clicking this link opens the New Code Review screen. From here, one or more reviewers can be assigned by either typing in the person's name or selecting it from the drop-down list. You can add a description to the review request.  When the request is submitted, it will show up as a code review request in the reviewer's My Work screen.
  • 21. What's new in TFS 2012 Detect Changes to Files or solution folder
  • 22. Microsoft Team Explorer Everywhere for TFS  IDE’s based on Eclipse 3.5 to 3.7 on Windows, Linux, Mac OS X, Solaris, AIX, or HP-UX.  Any of the following versions of the Java runtime:  Sun Java™ 1.5 to 6, or IBM Java™ 1.5 to 6 on Microsoft Windows  Apple Java™ 1.5 to 6 on Mac OS X  Sun Java™ 1.5 to 6 on Linux or Solaris  IBM Java™ 1.5 to 6 on Linux or AIX  HP Java™ 1.5 to 6 on HP-UX  Works with Visual Studio Team Foundation Server 2012 RC, Visual Studio Team Foundation Service Preview, Visual Studio Team Foundation Server 2010 or Visual Studio 2008 Team Foundation Server.
  • 23. Microsoft Team Explorer Everywhere for TFS
  • 24. Project Testing Audience - 1. Testers 2. QA Engineers 3. Developers
  • 25. MS Test Manager  Define Testing Effort  Create and Run Manual Tests  Record Manual Test Steps for Playback  Create Automated UI Tests  Create Physical or Virtual Test Environments To Use To Deploy Your Application or Run Your Tests  Collect Diagnostic Data or Affect Your Test Machine and Easily Add Collected Data to a Bug  Group Your Automated Tests By Using Test Categories
  • 27. What’s new in Unit Testing  Smart Test Discovery  Previously, when a test project was built, Test Explorer would perform an exhaustive search to discover the tests. A Smart Test Discovery algorithm has been implemented that significantly improves the time required for updates to appear on the Test Explorer Window.  Run Tests After Build a.k.a Continuous Test Runner  When this feature is turned on, the tests are run automatically after every successful build. If there are failed tests from previous runs, they are executed first.
  • 28. JavaScript Unit Tests on TFS with Chutzpah – Leverages VS 2012 – Build Summary. functionality to discover and run unit tests
  • 29. HP QC to TFS Migration  Scrat  Scrat converts and migrates all of your HP Quality Center projects and items over to Microsoft Team Foundation Server 2010.  The migration is quick, easy and a safe process that completes in just a few hours.  Contrary to the manual migration traditionally employed by organizations, Scrat fully automates the process.
  • 30. Scrat
  • 31. Garter Positions Microsoft in ALM Leaders Quadrant  Gartner, a leading industry analyst firm, evaluated 16 vendors based on their completeness of vision and ability to execute in the Magic Quadrant for Application Lifecycle Management.  Complete report details available at http://www.gartner.com/techno logy/reprints.do?id=1- 1ASCXON&ct=120606&st=sb
  • 32. Conclusion  Integrated ALM using Microsoft technologies improves the overall development efficiency by up to 30%.  All in One Solution provides the best overall value and utility versus point solutions because start-up and recurring costs are normally less, features are better integrated, and reporting is much more seamless and robust.
  • 33. References 1. http://support.smartbear.com/resources/sp/All-in-One.pdf 2. http://www.codeproject.com/Articles/304883/The-Future-of- Testing-Quality-Center-vs-Team-Found 3. http://www.hp.com/hpinfo/newsroom/press_kits/2010/HPSoftwar eUniverseBarcelona2010/Whats_new_in_HP_Application.pdf 4. http://www.microsoft.com/visualstudio/en-us/products/2010- editions/team-foundation-server/features 5. http://go.microsoft.com/?linkid=9747928 6. http://msdn.microsoft.com/en-us/library/bb385832.aspx 7. http://www.devproconnections.com/content1/topic/tfs-2012- 143104/catpath/visual-studio-2011/page/2 8. http://www.microsoft.com/visualstudio/11/en- us/lifecycle/develop-test 9. http://blogs.msdn.com/b/bharry/archive/2012/05/31/visual-studio- tfs-2012-release-candidate-available-today.aspx