BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DevOps.com - ECPv5.16.4//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:DevOps.com
X-ORIGINAL-URL:https://devops.com
X-WR-CALDESC:Events for DevOps.com
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20190310T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20191103T060000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20190314T130000
DTEND;TZID=America/New_York:20190314T140000
DTSTAMP:20260821T004134
CREATED:20190222T013526Z
LAST-MODIFIED:20190907T051541Z
UID:128034-1552568400-1552572000@devops.com
SUMMARY:Continuous Delivery: The One Question You Must Answer
DESCRIPTION:Most developers would tell you that their code is ready to release at any time. Most testers would disagree. This leads us to the single most important question associated with Continuous Delivery: \nDoes the release candidate have an acceptable level of risk? \nIn a highly-automated\, rapid delivery process\, you can’t make release decisions based on multiple\, independent\, and primarily binary (pass or fail) tests. You need a rapid assessment of the impact to the end-user experience—and immediate insight into whether releasing a particular build could cause palpable damage to the business. \nIf you’re not confident that you can answer this critical question accurately—on-demand—then join Wayne Ariola to learn how you can attain the required insight.  You will learn: \n\nHow to establish a baseline to measure risk in the context of application delivery\nHow risk coverage differs from code and test coverage\nWhy\, where\, and how to measure risk within the automated release process\n\n 
URL:https://devops.com/webinars/removing-the-devops-testing-bottleneck-lessons-from-experian/
CATEGORIES:2019 Webinars
ATTACH;FMTTYPE=image/jpeg:https://devops.com/wp-content/uploads/2019/02/Continuous-Delivery-Question.jpg
END:VEVENT
END:VCALENDAR