Any suggestions, new modifications and 4 days to figure it out

[HeatherO]

Hi,
Ok I don't know if it's because this is my first time doing the consulting
thing and they know it so they take advantage of it. Anyways I have been
working on a project the past 2 weeks they told me today that basically what
I have been working on is part of it and now they want to change it yet
again. So any direction on their new changes and where to begin is
appreciated. Basically they want a macro that prompts for the person to
enter the loacation/name of the download file. Once enter the macro will go
through an excel spreadsheet and count all the data (which I know how to do
no problem). After it is finished another screen appears that says "There
are XXX accounts listed. do you want to prepare forms?" Y/N. If Y then I
have to take the excel sheet and move data into 2 different forms in word
(also have figured how to do that). Then once that finishes running another
prompt "Do you wish to prepare merge letters" Y/N if Yes then prompt for name
and location of letter document for merge. I just have one question with all
these prompts and screens can this all be done in word or am I looking at
more of a visual basic thing with word and excel macros. Sorry just treading
water here and as a new consultant I think I'm being taken advantage of a
little since I am not full time either. If anyone has suggestions can you
please share, I'm just a wee bit frustrated and annoyed tonight, and a little
concerned that this looks more like VB programming then macros??
TIA
Heather

 

[Jezebel]

Just step back a little and read what you wrote as if you knew nothing about
it. Not to put too fine a point on it, if this is the standard of
specification you're working to, then you're going to be pushing sh*t uphill
however you go.

Consulting is all about changing demands; client expectations are always a
movable feast. Your key task as a consultant is to nail down what it is that
the they actually want and need, given that they usually don't know
themselves. The problem is always more about WHAT to do than HOW to do it.
If you leapt in and starting writing code with an objective as ill-defined
as the spiel you posted, then it's no wonder you and the client are at odds:
you're not clear on where you want to end up; they're not clear on what
you're doing for them. Maybe they are taking advantage of you; but more
likely it's just poor communication on both sides -- and as the consultant,
that's your responsibility.

 

[HeatherO]

Thanks Jezebel, you do have a point, about consulting. This is my first
attempt and it will be my last. I am only doing this part time, and I
shouldn't complain. Thanks for the constructive comments. I'll try to focus
and it a little better.
Heather

 

[Jonathan West]

Hi heather

The hardest part of being a consultant & doing this kind of thing
professionally is getting the feature spec nailed down - i.e. both stable
and commonly understood between you and the customer.

If you have delivered work based on a product spec that has now been
superseded, you have every right to revise your quotation for the job before
you deliver the work to the new specification. if the deliverery dates are
impractical given the late change, you can and must say so. If you don't, it
can reasonably be assumed that they are OK for you.

The first time you do that with any customer, it concentrates their minds
wonderfully on whether they *really* need to make that change!

So, the first thing to do is go back to them and say "You have changed the
specification. I need to have the revised specification properly and
thoroughly written down so that I can prepare a revised quotation for you,
since my original quotation is now out of date. The revised quotation will
of necessity include the cost of any work I have already done which will now
be wasted."

If you want to make it running an independent business, you must have the
confidence to insist that the customer behaves reasonably, and also the
willingness to walk away from a job if the customer is persistently
unreasonable. Otherwise, the unreasonable customer gets a whole load of work
for nothing and you end up having to break promises to other (more
reasonable) customers.

As for the difference between macros and VBA programming, you write macros
in VBA, and if you don't feel comfortable doing a thorough job with the
language, well perhaps the decision to make this your last consulting job
may be wise.

 

[JBNewsGroup]

Hi Heather,

This is my 2 cents worth and may be a little off the subject.

I have been a consultant for more than 25 years and I must say do not be
discouraged. Consulting can be rewarding, profitable and fun. You are not
"locked" in a rut doing the same thing day in and day out. Also you have to
realize that you are usually called in because the client does not know how
to do a task. Now my 2 cents worth of tips.

1. On any new project I first take the client's specifications and read it
over carefully. I then prepare a document stating the scope, or objective,
of the project (what has to be accomplished) , stating any assumptions
(client's invariably leave things out or do not know what they are missing),
how the project will be done and a definition of the milestones (when a
particular part, or phase, of the project is considered complete). Sometimes
the specifications are given orally so taking good notes is essential and
this document then becomes extremely important. I also include a project
cost and fee schedule as part of this document. I then have the client sign
this document. Only then will I do any high level design.

2. Once the high level design (no low level details) is completed (another
document) I get approval from the client (another sign off) before
continuing. During this phase expect major and minor changes, but, that is
what this step is all about. If there are changes modify the document and
re-submit it. Do not continue until this step is complete and "signed off".

3. Once all the above "sign offs" are complete I then start low level
design and coding. At this stage I consider any major changes an
enhancement and therefore I charge as a new project. You have to decide if
it is a major or minor change and you have to make the client aware that
this may occur (stated in the first document). I consider a major change
being something like adding a new feature to the project.

4. I also make the client aware that some code used (mainly subroutines and
functions) are proprietary and belong to the consultant but "licensed" to
the client. In this way I have built a "toolbox" of routines that I can
use so I do not have to worry about the little stuff and concentrate on the
client's objective. These routines are global and not specific to the
project. The major code is the client's property. I have never had a client
say no to this.

5. Note about fee schedule. After a major design step is complete a
percentage of the total project cost is expected before I continue. The
steps I use are initial document, high level design, programming, testing,
acceptance.

Even with all the above steps things will change. It is the nature of the
business and if it delays the project you have to make the client understand
that it is his doing that the project is delayed. If it is because of
something you missed then a lot of midnight oil gets burned in order that
the schedule be kept.

I used to work as an independent outside consultant for IBM and this is
essentially the IBM way. I have never been "burned" on a project. I always
end up with some payment even if the project is cancelled and believe me it
can happen.

Anyway, that is my 2 cents. There are some books that can guide you through
the process but it is a lot of "school of hard knocks". The first project
is the hardest so do not get discouraged. It does get easier. Also make
sure you have a printed contract for your services and make sure that it too
is signed. I guess you notice that I have signed documents during the whole
process. This is essentially your "security blanket". There can be no
discussions about "Joe said this and Bob said that". In the states where I
have done work these signed documents are legally binding. I do not know
about all states.

One last note. Keep good written records regarding expenses. This is for
the IRS when it comes tax time.

Jerry B.