[dude]

How to use OO (if this is the best way) in keeping up with development and progress of a software application we are developing.

Maybe OO isn't the best to do this in but if anyone in the world would know, it is this forum, I hope. ;) Let me explain more.

We developed a nice little MS Access program to handle our inventory a few years back. Now, we have decided to make a leap forward and redevelop that application using another program like MS Access (but way better and lets the end user use a web browser therefore decreasing our dependency on windows but increasing our ability to work from anywhere).

The problem I face is this: I co-manage the project but I am responsible for populating the list with everything that needs to be done. I currently keep a small list in outline format with line items that need to be implemented or addressed (new features, bugs, UI tweaks, etc.). When the item has been completed, I simply color the font a light shad of grey and leave it on there for a few weeks then eventually it just fades away into oblivion.

There has to be a better way to manage a project than the way I am doing it so I can go back and review completed items (we do track the dates FYI) and bug reports for curiosity or to see if we are repeating history all while being able to disseminate a PDF list to everyone in order for them to keep working on their part of the puzzle.

I have thought about OF but I am not real sure if this would be the way to go either. In my head, I see myself using some super cool future version of OO to handle this easily.

Anyone have a take on this? I feel there is a better way.