<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>PGS Software &#187; bugfix</title>
	<atom:link href="http://www.pgs-soft.com/tag/bugfix/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pgs-soft.com</link>
	<description>Nearshore Outsourcing IT Company - Offshore Development</description>
	<lastBuildDate>Fri, 30 Jul 2010 09:54:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>&#8220;That&#8217;s only a layout issue, we&#8217;ll fix it later&#8221;</title>
		<link>http://www.pgs-soft.com/thats-only-a-layout-issue-well-fix-it-later.html</link>
		<comments>http://www.pgs-soft.com/thats-only-a-layout-issue-well-fix-it-later.html#comments</comments>
		<pubDate>Tue, 23 Jun 2009 11:28:38 +0000</pubDate>
		<dc:creator>gwidziszowski</dc:creator>
				<category><![CDATA[Developers]]></category>
		<category><![CDATA[bugfix]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[layout]]></category>

		<guid isPermaLink="false">http://www.pgs-soft.com/?p=2573</guid>
		<description><![CDATA[I’m sure either you have said or heard such a sentence. It’s well known that functionality is the key part of an application. You can’t do much with good-looking screenshots. Most of developers focus on having the functionality implemented as efficiently as possible. I do it, probably you do so as well. It often happens [...]]]></description>
			<content:encoded><![CDATA[<div class="tweetmeme_button" style="float: right; margin-left: 10px; margin-top: 5px;">
			<a href="http://api.tweetmeme.com/share?url=http%3A%2F%2Fwww.pgs-soft.com%2Fthats-only-a-layout-issue-well-fix-it-later.html"><br />
				<img src="http://api.tweetmeme.com/imagebutton.gif?url=http%3A%2F%2Fwww.pgs-soft.com%2Fthats-only-a-layout-issue-well-fix-it-later.html&amp;source=pgssoftware&amp;style=normal&amp;service=bit.ly" height="61" width="50" /><br />
			</a>
		</div>
<p>I’m sure either you have said or heard such a sentence. It’s well known that functionality is the key part of an application. You can’t do much with good-looking screenshots. Most of developers focus on having the functionality implemented as efficiently as possible. I do it, probably you do so as well.</p>
<p>It often happens that although there is a design ready for the application, we don’t implement it because there are still lots of functional issues pending. Well – we can’t be blamed for this. In majority of cases the functionality that has to be implemented requires much more work than the look &amp; feel. It’s obvious that we want the difficult parts to be solved at first.</p>
<p>It’s all true, but what do you know about what the client thinks? When doing projects in<a title="PGS" href="http://www.pgs-soft.com" target="_blank"> PGS</a>, most of clients followed the standard path: functionality first, design later on. Recently, I have decided to do a experiment: we implemented as much of the design as possible before all the functionality was ready. The product was still in the bug-fixing phase, so it was not working correctly in all cases, occasionally it crashed (I guess you know what I mean), but the application had 90% of the design applied.</p>
<p>During the next partial delivery, it came out that the client became much more optimistic about the project when he saw it “looking nice”. I guess that the 20/80 rule ( 10/90 or whatever you like) applies here as well. It takes only 20% of time to implement the design, but it gives as much as 80% of the positive feedback from the client. Even when you application throws an error – a standard error page or window will cause the client to think</p>
<p><span style="color:#993300;">“<em>It’s not working at all!</em>”</span></p>
<p>while a nicely styled one, with some user-friendly message will result in</p>
<p><span style="color:#003300;">“<em>Uh-oh, an error, I must have done something wrong</em>”.</span></p>
<p>So next time, when you are working on a project – try to leverage the workload so that you can get more look &amp; feel ahead. I’m sure your client will appreciate this and so will you.</p>
<hr /><small>Copyright &copy; 2004 - 2010 by <a href="http://www.pgs-soft.com">PGS Software</a>
<br/><br/>
<a href="http://www.pgs-soft.com/thats-only-a-layout-issue-well-fix-it-later.html#comments">Comments (0)</a> - originally posted here <a href="http://www.pgs-soft.com/thats-only-a-layout-issue-well-fix-it-later.html">http://www.pgs-soft.com/thats-only-a-layout-issue-well-fix-it-later.html</a> </small>

<h2>Related posts</h2><ol><li><a href='http://www.pgs-soft.com/what-we-are-here-for.html' rel='bookmark' title='Permanent Link: What we are here for?'>What we are here for?</a></li>
<li><a href='http://www.pgs-soft.com/introduction-to-xval.html' rel='bookmark' title='Permanent Link: Introduction to xVal'>Introduction to xVal</a></li>
<li><a href='http://www.pgs-soft.com/estimation-of-software-development-projects.html' rel='bookmark' title='Permanent Link: Estimation of software development projects'>Estimation of software development projects</a></li>
</ol>]]></content:encoded>
			<wfw:commentRss>http://www.pgs-soft.com/thats-only-a-layout-issue-well-fix-it-later.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
