BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//pretalx.devconf.info//devconf-us-2026//talk//LQMHR9
BEGIN:VTIMEZONE
TZID:EST
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10;UNTIL=20061029T070000Z
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:STANDARD
DTSTART:20071104T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:EST
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000402T030000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=4;UNTIL=20060402T080000Z
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
BEGIN:DAYLIGHT
DTSTART:20070311T030000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:EDT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-devconf-us-2026-LQMHR9@pretalx.devconf.info
DTSTART;TZID=EST:20260925T090000
DTEND;TZID=EST:20260925T093500
DESCRIPTION:Agile tools like Jira excel at tracking work as it moves from "
 To Do" to "Done". But when we rely on tickets to capture context and decis
 ions made during task implementation\, the issue tracker also unintentiona
 lly becomes a store of knowledge. Communicating solely through tickets eli
 minates nuance and empathy\, and makes work more siloed and inhuman. This 
 talk explores common pitfalls\, strategies for managing knowledge outside 
 of Jira\, and techniques for using AI to reclaim and reorganize that knowl
 edge into a more human-centric workflow.
DTSTAMP:20260727T175100Z
LOCATION:Hewitt Boardroom (Capacity 35)
SUMMARY:Why Jira is a Terrible Knowledge Base: Using AI To Move Knowledge O
 ut of the Backlog - Kevin Howell
URL:https://pretalx.devconf.info/devconf-us-2026/talk/LQMHR9/
END:VEVENT
END:VCALENDAR