Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Cosa c'è di nuovo per l'Application Lifecycle Management in Visual Studio 2013
Similar to Cosa c'è di nuovo per l'Application Lifecycle Management in Visual Studio 2013 (20)
Recently uploaded
Recently uploaded (20)
Cosa c'è di nuovo per l'Application Lifecycle Management in Visual Studio 2013
- 2. Application lifecycle - tendenze
- 4. Aggiornamenti frequenti per prodotti on-premises/boxed Visual Studio 2012 Launch Settembre 2012 DevOps capabilities with Visual Studio 2012 System Center 2012 Update 1 SP1 Ottobre 2012 Novembre 2012 Gennaio 2013 Visual Studio 2012 Update 2 Marzo 2013 Visual Studio 2012 Update 3 Giugno 2013 rilasci basati su sprint tri-settimanali (3-week service delivery sprints) Visual Studio Online (aka TFS Service) Visual Studio 2013 Launch Novembre 2013
- 14. Plan REQUIREMENTS Develop Construct Operate Distribuzioni basate su configurazione Operate WORKING SOFTWARE
- 15. Plan REQUIREMENTS Develop Construct Operate Distribuzioni basate su configurazione Operate WORKING SOFTWARE
- 18. Continuous value Plan Operate REQUIREMENTS Agile portfolio management Kanban customization Work item tagging Work item charting Visual Studio and System Center integration Performance events Build | Measure | Learn Construct Develop Team Room Git CodeLens .NET memory dump analyzer Load testing as a service Collaborate Operate Release Integrated release management Configurationbased deployments WORKING SOFTWARE
- 19. Version control (TFVC or Git) Comment on changesets & commitsNew! Work item tracking and tagging Team rooms New! Agile planning tools Feedback Management New! Agile Portfolio Management* Build* Web-based test case management* New! Load testing* * Capability in preview – limits may apply. Authoring load tests requires Visual Studio Ultimate 2013 Preview.
- 20. Feedback o feedback su: • http://xedotnet.org/feedback o codice feedback: o email: 10 davide@knodev.com o website: feedback DEC06 www.knodev.com o blog: blog.knodev.com o twitter: @knodev
Editor's Notes
- In this session, we’ll take a look at all the advancements Microsoft has made in application lifecycle management over the past year.
- Le applicazioni, e le aspettativedegliutenti a loro associate, sonoevolutesignificativamentenegliultimianni. Cisiaspettache le applicazionifunzionino in differentipiattaforme, ci siaspettache I datisianosempredisponibili, e l’integrazione con glistrumenti social incorporatanellenostresoluzioni. Inoltre, datoche le esigenze del business e le tecnologiecambianorapidamente, glisviluppatoridevonoessere in grado di rilasciarevelocementevaloreaiclientiintegrandoi feedback nelprocessodecisionale/produttivo.
- Build-Measure-Learnèstatoconiato in “The Lean Startup”, da Eric Ries. Anche se quantotrattatonellibroèprincipalmenteindirizzatoagliambienti startup, alcuniaspettopossonoessereapplicatii in modogenerico per rilasciarevalorerapidamente. L’ideaprincipale qui èchel’agilitàpuòessereraggiuntainteragendovelocementeattraversoquestopassi di alto livello.Le funzionalità ALM di Team Foundation Server e Visual Studio aiutano le organizzazioniattraversoquestequattro diverse fasi –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.
- 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.
- Agile project managementAgile portfolio managementKanban boardsWork item taggingWork item charting
- 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.
- 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.
- See script. If the event also includes a “What’s New in VS” talk, be sure not to duplicate demos.
- One of the key areas development teams often struggle with is load testing. Common questions they ask are:Does our application deliver the critical features required under expected load?What happens if we’re successful and the load is more than planned? Can we scale with more instances, or do we need fundamental architectural changes?Can we scale across the breadth of our usage scenarios, or do we have bottlenecks around DB access, 3rd party Web services, etc?What’s the right amount of capacity to plan for when we ship (so we don’t pay for too much)?In the past, there have been a variety of tools for conducting the tests required to answer these kinds of questions. However, the infrastructure setup required a lot of up-front payment, setup time, physical space, and more. Fortunately, Visual Studio Online now provides load testing that happens in the cloud, offering teams a quick and easy path to get these questions answered.
- 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.
- 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.
- 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.
- With the release of System Center 2012 R2, IntelliTrace has become more deeply integrated within the operations infrastructure. Not only do application performance monitoring events (also known as APM events) now use the IntelliTrace format natively, but the new Microsoft Monitoring Agent includes the full functionality of Visual Studio IntelliTrace Collector for gathering full application profiling traces. This means that you’ll be able to more easily collect APM events and open them directly from Visual Studio.
- When you look at the application lifecycle as a whole, Microsoft has delivered considerable value over the past year. Since the release of Visual Studio 2012, the focus on providing a more efficient experience for development team members of all disciplines has already begun to deliver great dividends.
- Visual Studio Onlinewas launched in 2012 and has since provided regular updates out in front of the on-premises Team Foundation Server. With some limited exceptions, Visual Studio Online provides virtually all of the mainstream use cases as TFS, and typically has preview features not yet available on-prem. Some features, such as load testing as a service, are only available via Visual Studio Online.The free plan for small teams was announced in October 2012 and supports teams of up to five users. Users with Ultimate, Premium, or Test Professional subscriptions to MSDN have their access included. You can learn more at visualstudio.com.