<div dir="ltr">Here at Datacom we have an Application Management unit that specifically addresses these concerns for a variety of clients, taking on the support as well as on-going development and maintenance of existing applications for them. This is not limited only to Delphi applications, obviously. I joined Datacom in part to extend and further establish a Delphi capability in this area and this is now being further expanded, hence the call for CV's I recently posted to the list. :)<div><br>The flip-side of that is that if there are developers/ISV's on this list who have clients/customers who have concerns in this area, then you might like to put them in touch with us, as we may be able to provide the assurances they need.<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 3 December 2014 at 17:24, Graham Marsden <span dir="ltr"><<a href="mailto:grahamarsden@gmail.com" target="_blank">grahamarsden@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div>Hi John C.<br><br></div>This is an interesting issue and often pursued by managers who themselves are of the ilk not to be in their position for very long. On a few occasions I have had this thrown at me when in fact there is no-one in the organsiation that pre-dates me, the "outside" contactor/developer. <br><br></div>It is a valid point and the client is of course wanting continuity in their application's function and development. I have used the fact that this DUG exits at all as an assurance that help is not far away in the form of Delphi expertise should the "big yellow bus" thing happen.<br><br></div>A more reassuring offering to the client would be the existence of a loose or tight association between two or more developers and an assurance that there would be a specific named somebody that your client could contact in such an event. <br><br>Even better would be to actually meet that person(s) as part of setting up the Risk Management Plan.<br><br></div>It is a bit ironic that people think that dealing with a software company is itself some kind of assurance when in fact IT employees tend to be quite mobile and so the connection from the bespoke application to the actual people that created it is often fairly temporary.<br><br></div><div>Regards<span class="HOEnZb"><font color="#888888"><br><br></font></span></div><span class="HOEnZb"><font color="#888888"><div>Graham Marsden<br></div><div><br></div><br><div><br><div><div><br><br></div></div></div></font></span></div>
<br>_______________________________________________<br>
NZ Borland Developers Group - Delphi mailing list<br>
Post: <a href="mailto:delphi@listserver.123.net.nz">delphi@listserver.123.net.nz</a><br>
Admin: <a href="http://delphi.org.nz/mailman/listinfo/delphi" target="_blank">http://delphi.org.nz/mailman/listinfo/delphi</a><br>
Unsubscribe: send an email to <a href="mailto:delphi-request@listserver.123.net.nz">delphi-request@listserver.123.net.nz</a> with Subject: unsubscribe<br></blockquote></div><br></div>