Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Cross-Platform Agile DevOps with Visual Studio Team Services

186 views

Published on

Learn how Microsoft's cloud version of the popular Team Foundation Services tool enables an agile, DevOps workflow that facilitates requirements gathering, continuous integration, continuous delivery and continuous deployment with a drag-and-drop interface. Jeremy demonstrates an automated gated deploy to Azure from source code hosted on GitHub.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Cross-Platform Agile DevOps with Visual Studio Team Services

  1. 1. VSTS for X-Plat Agile DevOps with CI/CD Jeremy Likness @JeremyLikness
  2. 2. Swag! • For chance to win … • Retweet an @iVisionAtl session reminder, or • Take a picture of this session and tweet with #CodeStock and @ivisionAtl, or • Retweet this video
  3. 3. About iVision A privately held, IT consulting firm headquartered in Midtown, Atlanta. At iVision, we seek to understand our clients’ business first. We work with clients to architect, transform and support their technology — enabling them to realize their vision of a better tomorrow. Jeremy Likness| Director of App Dev https://github.com/JeremyLikness http://bit.ly/coderblog The iVision Difference  Engineering Expertise  White Glove Service  Delivery Assurance  Flexible Business Model  Proven Partner Ecosystem  Culture & People About iVision
  4. 4. Agenda • Waterfall • Agile • DevOps • Visual Studio Team Services • Demos • Q&A
  5. 5. Old School Requirements •Dead trees Design •The architect Implementation •Black box Testing •Bugs Deployment •Works on my machine! Support •Can’t reproduce
  6. 6. Agile
  7. 7. Without DevOps Developer Server Admin
  8. 8. With DevOps
  9. 9. Terminology • Definition of Done – a well-defined contract for defining when functionality is ready for production • Continuous Integration – merging developer work into the main trunk • Gated check-in – it must build and (preferably) pass all automated unit tests to merge • Developers push frequently, at least once per day, ideally more • Continuous Delivery – automatic delivery of the application to satisfy the definition of done • Continuous Deployment – may be same as delivery, usually has the caveat of deployment to production
  10. 10. Definition of Done • Meet the acceptance criteria for each item. • No remaining bugs that are classified as severity 1 or 2 and priority 1. • Bug Severity • 1 – Bug causes system crash, data loss, or critical functionality breakage with no acceptable workaround. • 2 – Bug causes non-critical functionality breakage with no acceptable workaround or does not meet performance requirements. • 3 – Bug causes critical or non-critical functionality breakage with an acceptable workaround, or bug causes a minor usability issue. • Bug Priority • 1 – Related backlog item is critical for the successful release of the system based on approved acceptance criteria. • 2 – Related backlog item is important but not required for successful release. • 3 – It is not necessary to fix the bug or related backlog item before the release. • 4 – Work on the bug or related backlog item is deferred until the next release.
  11. 11. Continuous Integration Example
  12. 12. Recipes for Success • Agile workflow on the front-end • Automated Tests • Gated Check-ins • Continuous Integration and Deployment • Active Monitoring and Feedback • Feature Consumption Reporting • Appropriate Environments (Dev, QA, UAT, Staging, Production)
  13. 13. Example: VSTS and Amazon
  14. 14. Example: VSTS and Amazon
  15. 15. DevOps with VSTS
  16. 16. VSTS, Azure, and Continuous Deployment
  17. 17. Questions? http://ivision.com/author/jlikness https://twitter.com/jeremylikness https://linkedin.com/in/jeremy.likness http://stackoverflow.com/users/228918/jeremy-likness https://github.com/JeremyLikness http://csharperimage.jeremylikness.com/

×