BEGIN:VCALENDAR
PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 4.0//EN
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Phoenix
X-LIC-LOCATION:America/Phoenix
END:VTIMEZONE
BEGIN:VEVENT
DESCRIPTION:Perhaps one of the most misunderstood concepts for people new 
 to Agile (and even some not so new) is the concept of story points. It se
 ems that everyone remembers planning poker and playing with cards\, but t
 he real essence of what points are\, how to assign points\, when to assig
 n points\, how to use points to determine velocity\, what points mean to 
 upper management seem to be either forgotten or not properly trained from
  the start.\nLearning objectives:\n\n* Learn that points are not absolute
  but refer to relative size\n* Learn that points are almost always specif
 ic to a scrum team and should not be used to determine relative maturity 
 among teams\n* Learn that Planning Poker is perhaps the most inefficient 
 (though memorable) way to assign relative size\n* Learn other appropriate
  techniques for sizing\n* Learn to size with non-collocated teams (if you
  are stuck with such an arrangement)\n* Learn how to use points to plan l
 ong term potentiality\n* Learn how to explain points to others to dispel 
 prevalent myths
DTEND;TZID=America/Phoenix:20141018T104500
DTSTAMP:20260308T050721Z
DTSTART;TZID=America/Phoenix:20141018T094500
GEO:33.293070;-111.796620
LOCATION:Chandler - Gilbert Community College - IRN-125
ORGANIZER:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:Perhaps one of the most misunderstood concepts for people new to A
 gile (and even some not so new) is the concept of story points. It seems 
 that everyone remembers planning poker and playing with cards\, but the r
 eal essence of what points are\, how to assign points\, when to assign po
 ints\, how to use points to determine velocity\, what points mean to uppe
 r management seem to be either forgotten or not properly trained from the
  start.\nLearning objectives:\n\n* Learn that points are not absolute but
  refer to relative size\n* Learn that points are almost always specific t
 o a scrum team and should not be used to determine relative maturity amon
 g teams\n* Learn that Planning Poker is perhaps the most inefficient (tho
 ugh memorable) way to assign relative size\n* Learn other appropriate tec
 hniques for sizing\n* Learn to size with non-collocated teams (if you are
  stuck with such an arrangement)\n* Learn how to use points to plan long 
 term potentiality\n* Learn how to explain points to others to dispel prev
 alent myths
UID:9f5a64cc-66ff-442c-a5d0-1df808d9c5dc
END:VEVENT
END:VCALENDAR