BleepingComputer.com: problem with software programmer

I will try not to be long winded- My husband has been trying to get a software program developed now for 4 years. Two programmers down. And trying to start with another. We have tried to use people that were refered and thought they could be trusted to do the job. The second time we had (had) is the operative word, a project manager and a programmer. How when you know next to nothing about software development do you keep a project from falling apart.
1. Isn't there some kind of guide or template out there that states that step one is this -step 2 is this - and can give an outline that would tell us what we should expect a programmer to do, know and when and what we should be getting and expecting along the way to keep the project on course.

Quote

No. Other than normal rules of business. Maybe you should be looking at the terms under which you employ the programmers - what's in the contract? Put in clauses about acceptability, usability, support, delivery timeframe, penalties for non-performance, and so on. Hey if I can think of this any competent lawyer should be able to tie these guys in knots.

What kind of software are you talking about? Machine code? 4GL? Web page design? Maybe you should be taking the job to a company and getting a quote for the finished product rather than trying to find the right person to make it for you piece by piece?

These are just my personal thoughts, others more experienced than I may have specific suggestions.

I am a student.The most important thing for me is to study hard.Not only the books,but some practical exprience.I wish someday I can be hired by a famous computer company.

As a project manager I know the kinds of problems you go through. Here is a simple analysis of the project life cycle:

http://www.maxwideman.com/papers/plc-models/texts.htm

One of the best ways to manage a project is to learn to properly use software like MS Project to define and assign each step in the process. Even if you use outside resources to code, the preliminary definition and design of the program is really critical.
Regards,
John

Hello, does your husband hope to sell his product? i guess he probably doesm but if he doesn't you could put it out to the open source community.

There are different approaches, but since this is a small project ( I guess, if there is only one programmer working on it at a time ), I would make sure the following steps are followed:

- Write down what the program is supposed to do. What are the inputs, and what are the outputs. Break this down into major components of functionality.
- Have the programer write a proposal of how long each of the different components of the system will take.
- Ask for a mock-up (prototype) of the application, if possible.
- Ask for status reports every 2 weeks, and what he/she intends to do for the next 2 weeks.
- Get an explanation why things are late. (And there will always be late deliverables, that's just the name of the game).
- If your specs are unclear, or if you change direction/features during development, expect delays.