What's new in ALM using Visual Studio 2013 and TFS 2013
•Télécharger en tant que PPTX, PDF•
1 j'aime•2,555 vues
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à What's new in ALM using Visual Studio 2013 and TFS 2013
Similaire à What's new in ALM using Visual Studio 2013 and TFS 2013 (20)
Plus de Microsoft Visual Studio
Plus de Microsoft Visual Studio (10)
Dernier
Dernier (20)
What's new in ALM using Visual Studio 2013 and TFS 2013
- 4. Frequent updates for on-premises/boxed products Visual Studio 2012 Launch September 2012 DevOps Visual Studio 2012 capabilities with System Center Update 1 2012 SP1 October 2012 November 2012 January 2013 Visual Studio 2012 Visual Studio 2012 Visual Studio 2013 Update 2 Update 3 Launch March 2013 3-week service delivery sprints Visual Studio Online June 2013 November 2013
- 16. Continuous value Plan Operate REQUIREMENTS Agile portfolio management Kanban customization Work item tagging BACKLOG Visual Studio and System Center integration Performance events Work item charting Build | Measure | Learn Construct Develop Team Room Git CodeLens .NET memory dump analyzer Load testing as a service Operate Collaborate Release RELEASE WORKING SOFTWARE Integrated release management Configuration-based deployments
Notes de l'éditeur
- In this session, we’ll take a look at all the advancements Microsoft has made in application lifecycle management over the past year.
- Build-Measure-Learn was coined in “The Lean Startup”, by Eric Ries. Although the discussion in the book is primarily focused on startup environments, aspects of it can be applied generally to help deliver value quickly. The main idea here is that agility can be achieved by iterating quickly through these high-level steps.The ALM capabilities of Team Foundation Server and Visual Studio help organizations through four different stages – Planning, Development, Release and Operations.
- Commitment to more frequent product updates shows that Build, Measure, Learn and agile development practices are being applied within Microsoft. Updates to Visual Studio Online are now occurring every few weeks.Given the higher-frequency of updates, organizations may need to make some changes to the way they evaluate new versions of development tools. There may be no “right time” to make the necessary upgrades and modify internal processes, so organizations will need to quickly match their needs with the current offering in order to make a decision. Some organizations may update as quickly as updates arrive, while others will be more selective. To help support these decisions, quite a bit of work goes into maintaining backwards compatibility with the previous major update, and different versions of Visual Studio can be installed side-by-side when needed.
- In this presentation, we will demonstrate each of these steps in more detail while highlighting the new features and capabilities of Team Foundation Server and Visual Studio 2013, as well as some of the highlights from the 2012 updates.
- Team Foundation Server 2012 focused mostly on improving the toolset for individual teams – managing backlogs, sprints, team capacity. Scaling out the agile project management toolset is a focus in TFS 2013 – agile portfolio management of multiple, hierarchical backlogs, and the rollup of work from across all agile teams.
- Agile project managementAgile portfolio managementKanban boardsWork item taggingWork item charting
- As we’ve seen from the previous demo, TFS continues to deliver a great variety of features that improve the planning process. Agile portfolio management provides a clean, intuitive way for project members of all disciplines to quickly and easily participate in each project. Kanban customization offers the ability to not only leverage Kanban in agile projects, but also adjust it as needed to best suit your preferred development model. Finally, we also took a look at work item tagging, a flexible way to organize and address growing project backlogs.
- After planning, teams dive into the development process. And while there have been great strides in individual developer productivity for decades, there is still a great deal of room for improvement when it comes to managing increasingly complex teams and projects. More teams are going distributed—whether across the town or across the globe—and tools need to better support that. The projects these teams work on are more sophisticated than ever, resulting in solutions with complex projects, processes, and codebases. And as with any project, quality needs to be built into the process as early and effectively as possible to ensure the best result.
- See script. If the event also includes a “What’s New in VS” talk, be sure not to duplicate demos.
- Microsoft has long had a core strength in the development phase of projects. Tools like Visual Studio have been enabling developers to be wildly productive for years, and the 2013 release introduces even more. However, Microsoft’s commitment to ALM reaches beyond the individual developer to help support their teams in ways that drive drastic improvements in project quality across the board. We’ve seen how team rooms provide a great way to bridge the gaps for distributed teams. Features like the flexible source control provided via TFS and Git offer developers a good way to manage complex codebases. And along with a ton of great features for testing, Visual Studio Online’s load testing as a service helps teams adopt an efficient testing plan from the earliest project sprints.
- As projects have become more agile, everyone wants to see more releases and have better insight into project status. The technology team wants to close work items and move on to new ones. Management wants to see the project progress for themselves. Customers want to get new features and bug fixes as soon as possible. Getting these releases out in a predictable and efficient way can bring home the true value of “continuous delivery”, helping everyone to get more out of the lifecycle.Unfortunately, creating a smooth, reliable, and repeatable release process for complex applications is a challenge faced by many organizations. They often discover that it requires a team of people just to manage the difficulties of building, releasing, and maintaining the various environments and deployment plans. Even then, the process is often very complex and difficult to sustain as they evolve. Finally, the need for transparency also needs to be accounted for, resulting in yet-another-project to develop and maintain.
- InRelease is a continuous deployment solution for .NET teams. It helps automate the deployment process and helps teams manage multiple environments. It also introduces a level of collaboration cross the release process, as well as providing an array or analytics and reporting. It was originally launched in 2009 and was acquired in the summer of 2013.
- InRelease technology will ultimately be transformed and integrated into Team Foundation Server. The release management authoring components will be included in Visual Studio Test Professional, Visual Studio Premium, and Visual Studio Ultimate. Everything needed to participate in a release process will be included in the Team Foundation Server CAL. Server components will be integrated into Team Foundation Server 2013. The deployers (which are required for each node you deploy on) will continue to be licensed separately.
- One major benefit of the new Release Management Server for Team Foundation Server 2013 is that it provides all the automated deployment goodness we were discussing earlier.
- It also ensures that the deployments are pushed out the same way to all stages.
- Not only does it automate the overall workflow, but it provides the ability to automate approvals where necessary, such as early phase deployments. You can still keep manual approvals for deployments deeper in the release cycle.
- Finally, the whole process is recorded so that you can enjoy full traceability throughout the process. This is extremely valuable in scenarios where there are strict compliance requirements for legal or other reasons.
- See script.
- Microsoft has made great strides in the area of release management since the launch of Visual Studio 2012. Not only have the core tools for project configuration and deployment improved, but Microsoft also acquired InRelease, a release management solution that is already deeply integrated with Visual Studio 2013 and Team Foundation Server 2013. These features provide a convenient way for development teams to define environments and then run deployments across them, whether manually, scheduled, or otherwise. The release process is extremely configurable, allowing for virtually any deployment contingency, custom process, rollback/rollforward, and more.
- Once an application is deployed to a production environment, the operations team is responsible for ongoing monitoring and maintenance. Inevitably, problems will occur, and it is often up to the operations team to diagnose and fix them. Some classes of problems, such as with hardware infrastructure, are in their direct scope. However, when the problems are in the software, the operations team needs to involve the development team themselves. Unfortunately, troubleshooting applications in production has been historically difficult, especially when the application itself was not proactively instrumented for this particular scenario.
- Existing tools include:IntelliTrace in ProductionNew tools include:Memory dump analysis for managed code
- Microsoft’s investment in integration between Team Foundation Server and System Center results in a much more robust operations experience for technology groups. It’s now much easier for IT teams to efficiently provide development teams with the actionable diagnostics they need when troubleshooting production applications, as well as more data for planning their next iteration.
- Convert the URL to simpler AKA URL.Like aka.ms/almvms