﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Adi commented on As intended, not as expected</title><description>I guess the phrase "The customer is always right" doesn't apply here...
</description><link>http://ayende.com/2592/as-intended-not-as-expected#comment2</link><guid>http://ayende.com/2592/as-intended-not-as-expected#comment2</guid><pubDate>Sun, 24 Jun 2007 20:40:21 GMT</pubDate></item><item><title>Roy Tate commented on As intended, not as expected</title><description>I have seen this in cases where the customer was implementing a new process (so they had never done this before) and also when I had optimized a step (they expected to export an order file, then import it again, but I piped the data straight into the order processing system).  Sometimes a report or a summary screen that gives a good overview of some internal operation will give the customer the confidence to accept your implementation of the process.  Managing customer expectations is an ART, and I don't always do a good  job when I am also the only developer on the project.  It's all about communicating and managing expectations.  If you do that well during the early phases of a project, the customer will usually be pleased by the results.
</description><link>http://ayende.com/2592/as-intended-not-as-expected#comment1</link><guid>http://ayende.com/2592/as-intended-not-as-expected#comment1</guid><pubDate>Sun, 24 Jun 2007 19:51:47 GMT</pubDate></item></channel></rss>