BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Salt Lake DevOps - ECPv6.10.1.1//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-ORIGINAL-URL:https://slcdevopsdays.org
X-WR-CALDESC:Events for Salt Lake DevOps
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-Robots-Tag:noindex
X-PUBLISHED-TTL:PT1H
BEGIN:VTIMEZONE
TZID:America/Denver
BEGIN:DAYLIGHT
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
TZNAME:MDT
DTSTART:20220313T090000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
TZNAME:MST
DTSTART:20221106T080000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Denver:20220914T180000
DTEND;TZID=America/Denver:20220914T190000
DTSTAMP:20260514T063147
CREATED:20220721T161421Z
LAST-MODIFIED:20220721T161816Z
UID:65-1663178400-1663182000@slcdevopsdays.org
SUMMARY:What to do about Brent? Identifying bottlenecks in your pipeline
DESCRIPTION:In the award winning DevOps book\, “The Phoenix Project”\, the authors tie together the best practices used by successful manufacturing companies and apply them to a fictional IT project. The concepts from the book have been one of the primary drivers for today’s DevOps organizational transformations.\nThe character “Brent” represents a critical IT resource that knows everything about the project\, is the fastest to implement a solution\, and generally the most helpful individual in the organization. Unfortunately\, Brent’s talents create a significant bottleneck for the organization.\nIn this presentation we will discuss ways to identify bottlenecks and how we can help organizations realize the true costs these constraints create. IT bottlenecks can often be difficult to identify as they may be hidden in the organization (purposely or ignorantly). Bottlenecks can be created by organizational structures\, antiquated procedures\, technical debt\, lack of personnel training\, etc.\nWe will also review the principles that derive all DevOps patterns known as the “Three Ways”. \nContinuously find and implement ways to improve delivery\nGet fast feedback and work from the strong failure signals to ever-weaker failure signals to get advance warning of quality issues.\nUse efficiencies gained from the first two ways to introduce rapid experiments that create qualitative gains
URL:https://slcdevopsdays.org/event/what-to-do-about-brent-identifying-bottlenecks-in-your-pipeline/
LOCATION:UT
END:VEVENT
END:VCALENDAR