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:This workshop teaches an approach to product development that considers the needs and goals of Product Management (PM)\, User eXperienc e Designers (UX)\, and Software Developers. This Integrated Development A pproach gets all three disciplines working together. The approach address es three iterative and overlapping activities: Product Research\, Product Design\, and Product Implementation. \; \; \; \;1. Product Research - determines “\;Target Users”\; and the “\;Target Benefits”\; they are expecting from the software\; \; \;2. P roduct Design - determines the functionality needed to achieve Target Ben efits (i.e.\, it produces draft interaction designs and a story map)\; 3\; \;3. Product Implementation - refines interaction designs and imp lements the highest-priority features. \; \; \; \;Unique to o ur approach is a consensus reaching technique known as the Point of View (POV) process (by Richard Tripp). The POV process is a technique for reac hing consensus in a fixed time-frame. The technique consists of individua ls on the team forming an “\;Individual Point of View”\; (IPOV) . Then\, using consensus building techniques\, the team transforms the In dividual Points of View into a single “\;Team Point of View”\; (TPOV). \; \; \; \;This approach benefits product development by providing the following: \; \;1. A set of techniques that help s PM identify and select both Target Users and Target Benefits (in the fo rm of epic user stories). Target Users and Target Benefits help PM focus on the important users and features of the software (i.e.\, those that ha ve the biggest ROI)\, and not just the loudest users. \; \;2. A sh ared vision and purpose among Product Management\, User eXperience Design \, and Agile Developers. This approach to a shared purpose helps people o n the team to better understand the customer\, the customer needs\, and w orking towards the same goal. \; \;3. A time-boxed iterative appro ach to reach an agreed-upon solution within a given time constraint. This benefit ensures that 1) design is appropriately considered - no more imp lementing with little to no thought\, and 2) time boxing keeps the team f rom over-analyzing. \; \; \; \;Presentation History \; \;+ This approach has been used at Infusionsoft for over two years. \; \;+ We have successfully taught this process to all Product Managers\ , UX Designers\, and Developers at Infusionsoft. DTEND;TZID=America/Phoenix:20121117T151500 DTSTAMP:20260609T081942Z DTSTART;TZID=America/Phoenix:20121117T141500 GEO:33.293070;-111.796620 LOCATION:Chandler - Gilbert Community College - IRN-232 ORGANIZER: SEQUENCE:0 STATUS:CONFIRMED SUMMARY:This workshop teaches an approach to product development that cons iders the needs and goals of Product Management (PM)\, User eXperience De signers (UX)\, and Software Developers. This Integrated Development Appro ach gets all three disciplines working together. The approach addresses t hree iterative and overlapping activities: Product Research\, Product Des ign\, and Product Implementation. \; \; \; \;1. Product Rese arch - determines “\;Target Users”\; and the “\;Target Ben efits”\; they are expecting from the software\; \; \;2. Produ ct Design - determines the functionality needed to achieve Target Benefit s (i.e.\, it produces draft interaction designs and a story map)\; \;& #10\;3. Product Implementation - refines interaction designs and impleme nts the highest-priority features. \; \; \; \;Unique to our a pproach is a consensus reaching technique known as the Point of View (POV ) process (by Richard Tripp). The POV process is a technique for reaching consensus in a fixed time-frame. The technique consists of individuals o n the team forming an “\;Individual Point of View”\; (IPOV). Th en\, using consensus building techniques\, the team transforms the Indivi dual Points of View into a single “\;Team Point of View”\; (TPO V). \; \; \; \;This approach benefits product development by providing the following: \; \;1. A set of techniques that helps PM identify and select both Target Users and Target Benefits (in the form o f epic user stories). Target Users and Target Benefits help PM focus on t he important users and features of the software (i.e.\, those that have t he biggest ROI)\, and not just the loudest users. \; \;2. A shared vision and purpose among Product Management\, User eXperience Design\, a nd Agile Developers. This approach to a shared purpose helps people on th e team to better understand the customer\, the customer needs\, and worki ng towards the same goal. \; \;3. A time-boxed iterative approach to reach an agreed-upon solution within a given time constraint. This ben efit ensures that 1) design is appropriately considered - no more impleme nting with little to no thought\, and 2) time boxing keeps the team from over-analyzing. \; \; \; \;Presentation History \; \;+ This approach has been used at Infusionsoft for over two years. \; \;+ We have successfully taught this process to all Product Managers\, UX Designers\, and Developers at Infusionsoft. UID:e77183b8-b41f-4ee6-abe9-c407a32d5bf3 END:VEVENT END:VCALENDAR