> I begin my big Y2k project on Monday. It starts off with
> a meeting with the client. They have already indicated
> that they want to see a project plan, testing plan, status
> reports, data file inventories, program file inventories,
> impact analysis, yada, yada, yada.
We've provided all that. It's really not that big of a deal. Just don't
use any programmer talent on this. A project admin is a *lot* cheaper
than a code cranker (not to mention easier to find.)
The project plan is obvious - you have to do that. Same can be said for
the test plan and the inventories. Without those you really will fail.
Make sure you build in time for new development. Don't assume that code
being written today is compliant. On my current project, we've handled
all the existing code. The main task now is setting up a review
procedure so the new stuff doesn't*it all up again.
Status reports can be huge time wasters. I don't let programmers do
status reports. I just ask them what they're up to and write it up
myself. Fortunately, this is the type of project where you can get some
pretty good feedback on where people are. They've either looked at a
file or they haven't. Not much room for dancing around an issue.
Impact analysis is the biggest waste. Avoid it if at all possible. If
the program is compliant, there's no impact. If not, it will fail. You
may want to make some triage decisions, but basically this is a no
brainer. Yet I see many organizations spending a lot of time on this. I
don't get it. Start fixing the most important stuff first. If you get it
all done early (as we did) great. Shut down the project and save some
Quote:> Sounds like they want something for the bookshelf that
> documents the failure of their project rather than a
> realistic possibility of success.
They're probably just looking for ammunition for when they tell the CEO
how much it's going to cost. That's their problem. Give them the
absolute minimum and let them ask questions if they want more.
Comsys Millenium Services
eMail: remove NoSpam from above
Standard disclaimer - I speak for myself and nobody else.