<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>DSpace Collection:</title>
    <link>http://hdl.handle.net/1880/45334</link>
    <description />
    <pubDate>Sat, 25 May 2013 22:17:09 GMT</pubDate>
    <dc:date>2013-05-25T22:17:09Z</dc:date>
    <item>
      <title>Build Notifications in Agile Environments</title>
      <link>http://hdl.handle.net/1880/45854</link>
      <description>Title: Build Notifications in Agile Environments
Authors: Ablett, Ruth; Maurer, Frank; Sharlin, Ehud; Denzinger, Joerg; Schock, Craig
Abstract: In an agile software development environment, developers write code 
that should work together to fulfill the wishes of the customer.  Continuous 
integration (CI) ensures that code from different individuals  integrates 
properly. CI compiles the entire codebase, deploys and tests it  with each 
change. CI alerts developers of any problems as errors can be  fixed more
easily  if caught earlier in the process. This paper compares the 
effectiveness of  different types of mechanisms for notifying developers to a 
successful or  unsuccessful build. Two different quantitative and qualitative 
user studies  were performed testing the effectiveness of three types of 
notification devices    one virtual e-mail based mechanism, one using ambient
lava  lamps, and one  robotic device. The results show that most developers
preferred  an easily  visible but unobtrusive ambient device combined with an
e-mail  describing the  problem in more detail.</description>
      <pubDate>Mon, 14 Jan 2008 00:00:00 GMT</pubDate>
      <guid isPermaLink="false">http://hdl.handle.net/1880/45854</guid>
      <dc:date>2008-01-14T00:00:00Z</dc:date>
    </item>
  </channel>
</rss>

