Project life cycle

Project life cycle steps

1.Define requirements

Talk to your client, and get to know what is your project about. You'll get most of requirements, but I suppose not all. Don't worry, you'll be filled in when project kicks in.

2. Define project cost

First of all, break all requirements in small tasks.  Then, estimate how long do you need on getting that task done. Sum all hours and add some more time (which I call "safety time"), which will secure you in case your tasks get longer than you anticipated. After you did thatmultiply it with your hourly rate. You should get your project cost.

3. Write specification

If you are developer, and are working with other developers it's crucial to have some sort of standard between you. Specification gives you project goals and requirements. You can also include some programming language standards which your team will follow. Big projects have special person which takes care of this and it is absolutely must have, but if you are working alone, it could use you to have written standards. If project needs maintenance, you can return and read specification and know exactly what you need to do.

4. Plan your project

When you were estimating your project cost, you have broken requirements in smaller pieces. Now you can use that smaller pieces and put it in calender. Estimate how much a day will you work, and put tasks according to they priority. Include holidays and weekends in planning. You are done with project preparations.

5. Start working

Take that tasks and start working. If you are developer don't forget about importance of planning out your classes.

6. Test it yourself

Write number of test and functionality your project needs to have, and do the testing. If you want, write down some bug list for future references. Maybe someday you'll be in the same position, having the same bug.

7. Have your client test it

It is important to have your client take a look of your project before it is finalized. That way you can get feedback from client and a new bug list.

8. Document your project

When you have finalized your project take some time to document about it. Update your specification and write help on how to use your project.

Final thought

I hope I summarized basic steps of having a project on your hands from beginning to the end. If you have any comments, or you do it some other way I would appreciate your thoughts and opinions.

Regards,
Vjeko