<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Boxes and Arrows: Comments by Julia Debari</title>
    <link>http://www.boxesandarrows.com/person/126992</link>
    <pubDate>Mon, 01 Feb 2010 18:54:30 GMT</pubDate>
    <description>Comments by Julia Debari</description>
    <item>
      <description>&lt;p&gt;I currently just ended a very Agile project and ran into many of the minefields discussed in this article. There was a sprint 0 for planning and the first day of every sprint we had an inception meeting. Unfortunately, 99% of it was spent on the developers. The UX team did work a sprint ahead, which worked well enough.&lt;br /&gt;I think one of the stickiest issues was that the business owners literally did not know what they wanted and went to the developers and asked them what could be done. The &amp;#8220;what&amp;#8221; was decided before the &amp;#8220;why&amp;#8221; which I think made for a much more complex situation. &lt;br /&gt;Looking back on the project, I think certain aspects of the project would have worked better if the UX team sat with the developers and sketched out what they wanted in real time. While very difficult, the idea of seeing the &amp;#8220;whole picture&amp;#8221; needed to be let go and the UX team should have worked in a more component based model.&lt;/p&gt;</description>
      <link>http://www.boxesandarrows.com/view/bringing-user#content_50241</link>
      <guid>http://www.boxesandarrows.com/view/bringing-user#content_50241</guid>
      <pubDate>Mon, 01 Feb 2010 18:54:30 GMT</pubDate>
      <author>Julia Debari</author>
    </item>
  </channel>
</rss>

