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:A key concept of any Agile methodology is communication. It&#8
 217\;s no longer normal or acceptable for developers to sit and develop a
 pplications in isolation from the business. To that end\, developers and 
 business domain experts have been trying to find better ways to communica
 te. While developers tend to speak in terms of &#8220\;code and technolog
 y&#8221\; most business domain experts are more comfortable communicating
  in terms of scenarios\, workflows and business rules.&#13\;&#10\; Test D
 riven Development (TDD) was the first step in getting these two groups to
  communicate in the same way. Developers could write unit tests that expr
 essed business requirements with the hope that business users could valid
 ate that what was being tested was in fact what the desired behavior was.
  But\, unit tests are still code and while it was better\, the communicat
 ion was still stilted and inefficient.&#13\;&#10\;&#13\;&#10\;To help thi
 s communication new techniques such as Behavior Driven Development (BDD) 
 and Acceptance Test Driven Development (ATDD) have become popular. Along 
 with these new ideas\, new tools like SpecFlow have become popular as a m
 eans to express unit tests in a way that the business can better understa
 nd and validate.&#13\;&#10\;&#13\;&#10\;This session will demonstrate how
  SpecFlow can be leveraged in your BDD or ATDD practices. The Gherkin lan
 guage and the &#8220\;Given\, When\, Then&#8221\; paradigm will be explai
 ned and you will see how to write tests in a way that business users are 
 not only capable of reading\, but can also help you create them.
DTEND;TZID=America/Phoenix:20140405T120000
DTSTAMP:20260608T025435Z
DTSTART;TZID=America/Phoenix:20140405T110000
GEO:33.293070;-111.796620
LOCATION:Chandler - Gilbert Community College - IRN-219
ORGANIZER:
SEQUENCE:0
STATUS:CONFIRMED
SUMMARY:A key concept of any Agile methodology is communication. It&#8217\
 ;s no longer normal or acceptable for developers to sit and develop appli
 cations in isolation from the business. To that end\, developers and busi
 ness domain experts have been trying to find better ways to communicate. 
 While developers tend to speak in terms of &#8220\;code and technology&#8
 221\; most business domain experts are more comfortable communicating in 
 terms of scenarios\, workflows and business rules.&#13\;&#10\; Test Drive
 n Development (TDD) was the first step in getting these two groups to com
 municate in the same way. Developers could write unit tests that expresse
 d business requirements with the hope that business users could validate 
 that what was being tested was in fact what the desired behavior was. But
 \, unit tests are still code and while it was better\, the communication 
 was still stilted and inefficient.&#13\;&#10\;&#13\;&#10\;To help this co
 mmunication new techniques such as Behavior Driven Development (BDD) and 
 Acceptance Test Driven Development (ATDD) have become popular. Along with
  these new ideas\, new tools like SpecFlow have become popular as a means
  to express unit tests in a way that the business can better understand a
 nd validate.&#13\;&#10\;&#13\;&#10\;This session will demonstrate how Spe
 cFlow can be leveraged in your BDD or ATDD practices. The Gherkin languag
 e and the &#8220\;Given\, When\, Then&#8221\; paradigm will be explained 
 and you will see how to write tests in a way that business users are not 
 only capable of reading\, but can also help you create them.
UID:6b8139c8-eb42-4190-822c-036187b28b68
END:VEVENT
END:VCALENDAR