Question on project organization

[Pests]

Im trying to get more organized in my projects that I'm working on. I installed a project management type thing, with tasks and all that good stuff. The script automatically set up 6 'Phases' of making my site: Concept, Planning, Development, Testing, Rollout, and Maintenance. I want to try to use a system like this, but I'm not sure what kind of tasks go into what things, and what I should record as a task. Can someone give me some examples or other help on this?

(I'm not sure if I posted this in right place. If someone would be kind enough to move it where you think it would get more replies, please do so. Thanks)

[laserlight]

You need to learn about the (or perhaps a) software development life cycle?
Using what you provided, a rough guide would be:

Concept
Define the goals of the project.
Consider the limitations of the situation.

Planning
Project structure, i.e. what modules/classes are to be written and how to interface between them.
Set any conventions, e.g. naming of page, use of global variables, coding style.

Development
Coding, duh.

Testing
By both the programmer and a group of initial testers.
Various testing methods, bugs found, missing features, poor UI, etc...

Rollout
Release of stable versions.

Maintenance
Post release bug fixes.
Adding extra features.
Going through the whole SDLC to revamp the project and create a better product based on the current.

Though frankly if you're only a hobbyist programmer, this is a little extreme.
And if you're not, it really depends on the situation, it should be individually analysed.

[Pests]

Thanks alot for the help. I seem to be able to know what to do when I get to it, and can't really list it before its done. But I have found some problems with this method and wish to better organize myself.