[AccessD] Re: Determining Time for Project

John W. Colby jwcolby at colbyconsulting.com
Thu Feb 26 09:07:17 CST 2004


The silly part of this whole thing is "the amount of time she initially
thought it would be".  That's like ME taking my car to my mechanic (I am NOT
a mechanic) and telling him how long it should take to swap out my engine.
How on God's green earth can she "think how long it will take"?

John W. Colby
www.ColbyConsulting.com

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Bryan
Carbonnell
Sent: Thursday, February 26, 2004 5:30 AM
To: Access Developers discussion and problemsolving
Subject: RE: Re: [AccessD] Re: Determining Time for Project


On 25 Feb 2004 at 10:30, Charlotte Foust wrote:

> Non-developers never understand why it takes so long.  They figure if
> they throw a few more people at it or leave out a few things, you can
> do it in a week ... Or a month ... Or 90 days ... Or whatever.  I

It wasn't so much she didn't understand why I needed that much time.

She seemed to understand that, it's just that she didn't like it.

We are undergoing some pretty significant changes in the department
and I get myself secconded for 4 times the amount of time she
initially thought it would be. That's why she didn't appreciate it.

Oh well, the seccondment was *HER* idea anyway :)

--
Bryan Carbonnell - carbonnb at sympatico.ca
Artificial intelligence is no match for natural stupidity.


--
_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com






More information about the AccessD mailing list