<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments for Boost Labs</title>
	<atom:link href="http://www.boostlabs.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.boostlabs.com</link>
	<description></description>
	<lastBuildDate>Thu, 30 Aug 2012 16:12:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Why the Design Phase Is the Underdog by Boost Labs</title>
		<link>http://www.boostlabs.com/why-the-design-phase-is-the-underdog/#comment-175</link>
		<dc:creator>Boost Labs</dc:creator>
		<pubDate>Thu, 30 Aug 2012 16:12:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=2109#comment-175</guid>
		<description><![CDATA[Thank you for your comment Steve.  We totally agree.  

In our opinion, execution should only be started when the business logic of the product is completely understood, which falls under the umbrella of “problem solving”.  This is where we feel the design process would be able to square away, which would serve as the overall foundation for the final product to evolve to.  Without it we have seen ciaos under Agile Development process that not only gives Agile a bad name, but also puts the product in danger of not launching.  

Just to be clear, design phase doesn’t necessarily include execution of design mocks every time.  It really depends on the project and the execution process needed.  In your example with Agile, we agree with what you are saying.

To answer your question about how much design is enough…  Again the major components that need to be identified during the design phase: the business logic of the product and client expectations, which includes: branding guidelines, sitemap, budget, timeline, ROI metrics, and design preferences.  From there the logical next step is design execution (mock designs, translation to code, etc).  Hope that answers your question.]]></description>
		<content:encoded><![CDATA[<p>Thank you for your comment Steve.  We totally agree.  </p>
<p>In our opinion, execution should only be started when the business logic of the product is completely understood, which falls under the umbrella of “problem solving”.  This is where we feel the design process would be able to square away, which would serve as the overall foundation for the final product to evolve to.  Without it we have seen ciaos under Agile Development process that not only gives Agile a bad name, but also puts the product in danger of not launching.  </p>
<p>Just to be clear, design phase doesn’t necessarily include execution of design mocks every time.  It really depends on the project and the execution process needed.  In your example with Agile, we agree with what you are saying.</p>
<p>To answer your question about how much design is enough…  Again the major components that need to be identified during the design phase: the business logic of the product and client expectations, which includes: branding guidelines, sitemap, budget, timeline, ROI metrics, and design preferences.  From there the logical next step is design execution (mock designs, translation to code, etc).  Hope that answers your question.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why the Design Phase Is the Underdog by Steve Andrews</title>
		<link>http://www.boostlabs.com/why-the-design-phase-is-the-underdog/#comment-174</link>
		<dc:creator>Steve Andrews</dc:creator>
		<pubDate>Thu, 30 Aug 2012 14:17:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=2109#comment-174</guid>
		<description><![CDATA[Great article.  I totally agree with your assertions that clients need to take the time and allocate the right budget for establishing the vision for their products before starting to build.  As a developer I do wonder how to square an up-front design phase with contemporary Agile development methods, which are based around the idea that the design will change during development as we learn more information about the problem space.

I wonder if the design phase is really more about helping the client get some clarity on what the &lt;i&gt;problem&lt;/i&gt; is and what a &lt;i&gt;candidate solution&lt;/i&gt; might look like more than a fine-grained specification of the solution and a project plan that are written in stone.

Once the problem is better understood and a candidate design is established we could then identify finer-grained user stories and put them in a product backlog, which is the central planning mechanism for Agile development projects.  This way we can achieve the best of both worlds: the client is investing the time and money to establish their vision, the candidate design provides a &quot;visual guide&quot;, and the resulting backlog gives us a way to evolve towards that design while at the same time allowing the flexibility to adapt the solution as we learn more during development based on actual end-user feedback.

Curious to know your thoughts, and it does beg the question: how much design is enough?]]></description>
		<content:encoded><![CDATA[<p>Great article.  I totally agree with your assertions that clients need to take the time and allocate the right budget for establishing the vision for their products before starting to build.  As a developer I do wonder how to square an up-front design phase with contemporary Agile development methods, which are based around the idea that the design will change during development as we learn more information about the problem space.</p>
<p>I wonder if the design phase is really more about helping the client get some clarity on what the <i>problem</i> is and what a <i>candidate solution</i> might look like more than a fine-grained specification of the solution and a project plan that are written in stone.</p>
<p>Once the problem is better understood and a candidate design is established we could then identify finer-grained user stories and put them in a product backlog, which is the central planning mechanism for Agile development projects.  This way we can achieve the best of both worlds: the client is investing the time and money to establish their vision, the candidate design provides a &#8220;visual guide&#8221;, and the resulting backlog gives us a way to evolve towards that design while at the same time allowing the flexibility to adapt the solution as we learn more during development based on actual end-user feedback.</p>
<p>Curious to know your thoughts, and it does beg the question: how much design is enough?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TopGear Infographic by Motivation... - FFCars.com : Factory Five Racing Discussion Forum</title>
		<link>http://www.boostlabs.com/topgear-infographic/#comment-126</link>
		<dc:creator>Motivation... - FFCars.com : Factory Five Racing Discussion Forum</dc:creator>
		<pubDate>Mon, 09 Jul 2012 12:52:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1852#comment-126</guid>
		<description><![CDATA[[...] maps at work. I&#039;ve got it hanging on the wall (it&#039;s about 6 foot tall) in my home office. TopGear Infographic - Boost Labs &#124; Boost Labs  Peace, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] maps at work. I&#039;ve got it hanging on the wall (it&#039;s about 6 foot tall) in my home office. TopGear Infographic &#8211; Boost Labs | Boost Labs  Peace, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TopGear Infographic by The Need for Visual Content &#124; Boost Labs</title>
		<link>http://www.boostlabs.com/topgear-infographic/#comment-104</link>
		<dc:creator>The Need for Visual Content &#124; Boost Labs</dc:creator>
		<pubDate>Thu, 28 Jun 2012 01:34:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1852#comment-104</guid>
		<description><![CDATA[[...] TopGear Infographic  Recent CommentsKevin on Why Geovisualization (Geographic Visualization) WorksSugel on TopGear InfographicJohn on TopGear InfographicChris on TopGear InfographicZach on TopGear InfographicArchives [...]]]></description>
		<content:encoded><![CDATA[<p>[...] TopGear Infographic  Recent CommentsKevin on Why Geovisualization (Geographic Visualization) WorksSugel on TopGear InfographicJohn on TopGear InfographicChris on TopGear InfographicZach on TopGear InfographicArchives [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Why Geovisualization (Geographic Visualization) Works by Kevin</title>
		<link>http://www.boostlabs.com/why-geovisualization-geographic-visualization-works/#comment-52</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Thu, 07 Jun 2012 01:52:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1911#comment-52</guid>
		<description><![CDATA[Geovisualizations are certainly the most user-recognizable way of displaying information relating to geography. However, as data display systems become more complex in the future, geographic representations will need to be 3-dimensional in order to display data accurately. All 2D representations of maps are inherently distorted. If you flattened a globe out to a web image, it enlarges the poles and shrinks the equator. Therefore the data being displayed in these regions is also distorted. Boost Labs is on the cutting edge of Geovisualizations and our backgrounds in technology will allow us to experiment with 3-Dimensional mapping systems in the near future.]]></description>
		<content:encoded><![CDATA[<p>Geovisualizations are certainly the most user-recognizable way of displaying information relating to geography. However, as data display systems become more complex in the future, geographic representations will need to be 3-dimensional in order to display data accurately. All 2D representations of maps are inherently distorted. If you flattened a globe out to a web image, it enlarges the poles and shrinks the equator. Therefore the data being displayed in these regions is also distorted. Boost Labs is on the cutting edge of Geovisualizations and our backgrounds in technology will allow us to experiment with 3-Dimensional mapping systems in the near future.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TopGear Infographic by Sugel</title>
		<link>http://www.boostlabs.com/topgear-infographic/#comment-48</link>
		<dc:creator>Sugel</dc:creator>
		<pubDate>Mon, 04 Jun 2012 14:29:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1852#comment-48</guid>
		<description><![CDATA[Without the &#039;sleeping fireman&#039; requirement the fastest time around the track for a road legal car would be the Caparo T1 . The Caparo posted a time of 1:10.6 despite its reliability problems.]]></description>
		<content:encoded><![CDATA[<p>Without the &#8216;sleeping fireman&#8217; requirement the fastest time around the track for a road legal car would be the Caparo T1 . The Caparo posted a time of 1:10.6 despite its reliability problems.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TopGear Infographic by John</title>
		<link>http://www.boostlabs.com/topgear-infographic/#comment-46</link>
		<dc:creator>John</dc:creator>
		<pubDate>Sun, 03 Jun 2012 21:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1852#comment-46</guid>
		<description><![CDATA[This would be great in AppStore]]></description>
		<content:encoded><![CDATA[<p>This would be great in AppStore</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TopGear Infographic by Chris</title>
		<link>http://www.boostlabs.com/topgear-infographic/#comment-44</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Wed, 30 May 2012 13:22:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1852#comment-44</guid>
		<description><![CDATA[Yes, that&#039;s correct. The only cars put on the visualization are production cars that are deemed as road-legal production.]]></description>
		<content:encoded><![CDATA[<p>Yes, that&#8217;s correct. The only cars put on the visualization are production cars that are deemed as road-legal production.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TopGear Infographic by Zach</title>
		<link>http://www.boostlabs.com/topgear-infographic/#comment-42</link>
		<dc:creator>Zach</dc:creator>
		<pubDate>Mon, 28 May 2012 23:32:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1852#comment-42</guid>
		<description><![CDATA[The F1 car is disqualified from the power lap leader-board because it is not a &#039;road-legal production car&#039; and it does not have &#039;sufficient ride height to clear a standard speed bump&#039;.  It did run an impressive time, they just couldn&#039;t put it on the board.

Wikipedia has an entry for the test track with info about the power lap rules: http://en.wikipedia.org/wiki/Top_Gear_test_track#Power_Laps]]></description>
		<content:encoded><![CDATA[<p>The F1 car is disqualified from the power lap leader-board because it is not a &#8216;road-legal production car&#8217; and it does not have &#8216;sufficient ride height to clear a standard speed bump&#8217;.  It did run an impressive time, they just couldn&#8217;t put it on the board.</p>
<p>Wikipedia has an entry for the test track with info about the power lap rules: <a href="http://en.wikipedia.org/wiki/Top_Gear_test_track#Power_Laps" rel="nofollow">http://en.wikipedia.org/wiki/Top_Gear_test_track#Power_Laps</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on TopGear Infographic by Boost Labs</title>
		<link>http://www.boostlabs.com/topgear-infographic/#comment-41</link>
		<dc:creator>Boost Labs</dc:creator>
		<pubDate>Mon, 28 May 2012 12:22:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.boostlabs.com/?p=1852#comment-41</guid>
		<description><![CDATA[Thank you for the feedback. We will add it to our review list and make the appropriate changes.]]></description>
		<content:encoded><![CDATA[<p>Thank you for the feedback. We will add it to our review list and make the appropriate changes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
