BEGIN:VCALENDAR
PRODID;X-RICAL-TZSOURCE=TZINFO:-//Calagator//EN
CALSCALE:GREGORIAN
X-WR-CALNAME:Calagator
METHOD:PUBLISH
VERSION:2.0
BEGIN:VTIMEZONE
TZID;X-RICAL-TZSOURCE=TZINFO:America/Los_Angeles
BEGIN:DAYLIGHT
DTSTART:20170312T020000
RDATE:20170312T020000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
CREATED;VALUE=DATE-TIME:20170508T014432Z
DTEND;TZID=America/Los_Angeles;VALUE=DATE-TIME:20170530T203000
DTSTART;TZID=America/Los_Angeles;VALUE=DATE-TIME:20170530T180000
DTSTAMP;VALUE=DATE-TIME:20170508T014432Z
LAST-MODIFIED;VALUE=DATE-TIME:20170508T014432Z
UID:http://calagator.org/events/1250471881
DESCRIPTION:Level up your skills\, network with peers\, and learn to acce
 lerate stakeholder value delivery with this unique workshop from nuCogni
 tive.&#13\;\n&#13\;\nThe first Agile principle is &quot\;Our highest pri
 ority is to satisfy the customer through early and continuous delivery o
 f valuable software.&quot\; However\, in practice this does not seem to 
 be true nearly as often as it should be. Teams often fail to provide ear
 ly\, frequent delivery of stakeholder value. Instead\, they focused on s
 pikes\, class libraries\, infrastructure\, and other inward-focused work
 \, without an understanding of their stakeholders and what they value. A
 s a result\, many teams start with what is most familiar\, easiest\, or 
 most convenient for them rather than what stakeholders value most.&#13\;
 \n&#13\;\nWhy do teams often become focused on (or even obsessed with) f
 eature development and maximizing development velocity? Without explicit
  focus on value\, the association between velocity\, feature development
 \, and value-delivery is weak - perhaps even non-existent. At best\, the
 se projects are conducted sub-optimally. Frequently\, they fail when sta
 keholders remove funding because they perceive a lack of value add.&#13\
 ;\n&#13\;\nValue-driven delivery is achieved using the answers to three 
 simple\, but not at all easy\, questions:&#13\;\n1. Who are your stakeho
 lders?&#13\;\n2. What do they value?&#13\;\n3. What are you doing in the
  next two weeks or less to provide value to them?&#13\;\n&#13\;\nTeams o
 ften have many more stakeholders than they first realize. Value-driven D
 elivery ensures those stakeholders are made explicit\, and that the list
  of stakeholders is kept current throughout the project.&#13\;\n&#13\;\n
 Value-driven delivery captures and maintains stakeholder values in a qua
 ntified\, verifiable way. This ensures that teams can know the real effe
 cts of each stakeholder value delivery\, and prevents work based on an o
 utdated understanding of value.&#13\;\n&#13\;\nValue-driven Delivery als
 o challenges teams to sequence deliveries so that they deliver the most 
 valuable things first. This can have tremendous benefits\, generating ea
 rly business results and reducing the time required for the team to get 
 into a positive Return on Investment for the project.&#13\;\n&#13\;\nVal
 ue-driven delivery makes a natural overlay for Scrum\, but does not requ
 ire Scrum's use to be effective. Value-driven delivery does not ignore f
 eatures and velocity\, but it explicitly places value delivery above tho
 se things as the top priority.&#13\;\n&#13\;\nTwo other advantages to Va
 lue-driven Delivery worth mentioning: First\, it is not limited to softw
 are\, but applies to all aspects of an organization\, including the exec
 utive suite\, human resources\, finance\, IT\, and product teams. Second
 \, it is not focused on or limited to any particular scale. In fact\, it
  is scale-free\, working on small teams and teams of more than 500 engin
 eers in a 100K-person company.&#13\;\n&#13\;\nLearning Outcomes:&#13\;\n
 -The definition and nature of value&#13\;\n-The principles and practices
  of Value-driven Delivery&#13\;\n-How to use Evolutionary Delivery to ma
 nage value-driven work\, alone or in concert with Scrum&#13\;\n-Fundamen
 tals of several disciplines and models that aid value-driven work\, incl
 uding the Kano Model\, elements from Diffusion of Innovations\, UX Proof
  Points\, and the HEART Framework&#13\;\n-Attendees will gain enough und
 erstanding to begin using Value-driven Delivery in their own work if the
 y desire.&#13\;\n-Additional sources of information will be provided for
  continued learning.&#13\;\n&#13\;\nWho should attend:&#13\;\nProduct ma
 nagement\, product owners\, product developers\, service designers\, arc
 hitects\, product managers\, engineers\, business development\, business
  strategy\, marketing\, planners\, project managers\, software developer
 s\n\nTags: product management\, Product Owners\, product developers\, se
 rvice designers\, architects\, Product managers\, engineers\, business d
 evelopment\, business strategy\, marketing\, planners\, project managers
 \, Software developers\, agile\, lean\n\nImported from: http://calagator
 .org/events/1250471881
URL:https://www.eventbrite.com/e/value-driven-delivery-mini-workshop-tick
 ets-33773095237
SUMMARY:Value-driven Delivery Mini-Workshop
LOCATION:Lucky Labrador Beer Hall: 1945 NW Quimby\, Portland OR 97209 US
SEQUENCE:1
END:VEVENT
END:VCALENDAR
