Access "To Do List" for developing

[norm]

Has anyone have any information for an add in or point me in the right
direction? What I am looking for is a "To Do List" for a database I am
working on..It would be a list of items I need to create in the particular
database and click them off as they are created. Something similar is
already incoperated in Fron Page, where you can assign individual items to a
developer and as it is completed, mark it of as "completed"

 

[Albert D. Kallal]

Actually a lot of us just fire up a excel sheet and use that.

Now course because I am a bit biased towards ms-access, then I often use
access itself.

Here is what a typical to do list looks like, and it only 3 columns:

RequestDate DoneDate Feature
5/1/2007 5/1/2007 Add birthday to contacts
5/1/2007 5/1/2007 Default email for sending invoice
5/1/2007 5/1/2007 use company name + invoice number for pdf
doc name when sending invoice
5/1/2007 5/3/2007 Calendar - must show all groups booked
(only shows first group now)

5/1/2007 5/3/2007 Change invoice text form confirmation number
to invoice number (make this config text)

5/3/2007 5/16/2007 Add 2nd phone number for pubs contacts
5/3/2007 5/16/2007 Display 2nd phone number on itinerary stops
5/3/2007 5/16/2007 Need to set default for pick to "no" drop-off
(make this a config option)


So, I just make very simple table, and put in the request date, and then
have a doneDate when I done the task. In some cases I add a few additional
columns to the such as to which client requested the change (if more then
one client is using the application). I often let the wizard build a few
reports on these tables and then I printout as to what I'm supposed to do
for the following week.

The above is an actual cut and paste from one of my applications, and the
table actually has hundreds of entries in it (the above is only a few
rows, but you can see the data structure is very simple. In fact, sometimes
I placed the table and the actual application for the client, and it serves
as a
historical documentation of features and tasks done...

I guess at the end of the day I believe keeping this as simple as possible
is the best approach.

 

[(PeteCresswell)]

Per norm:

What I am looking for is a "To Do List" for a database I am
working on..It would be a list of items I need to create in the particular
database and click them off as they are created.

I'm with Albert on keeping it simple.


I do, however, indulge myself in one extra little twist: my
To-To list is in the application itself in a table called:

"----------- Program Changes ------------"

Named so it both floats to the top and is obviously not really a
"Table" in the application/database sense.

Plain old Courier New ASCII text.

Each record is numbered according to the application's rev
number, so if I'm working on version 2.03 of the app, the current
record's ID is 203.

I even have a little form to display it.


Two sections:

DONE:
-----

and

TO-DO:
------


When a user asks for something new, I scribble madly on a legal
pad and then, as soon as I have time to myself, translate the
hand-written notes into very specific step-by-step descriptions
of what is needed to accomplish the change. One action: one
description. May sound a little obsessive, but it helps me
decompose the change and analyze it further as I do so.

As I complete each component of a change, I cut/paste it from
"TO-DO" up into the "DONE" section.

I find this especially useful bc I get co-opted many times during
the day when I'm in the middle of something. If I maintain the
TO-DO/DONE lists conscientiously, there's no problem getting
re-oriented when I finally can return to the task.

Also, FWIW, each version of the app has it's change history
embedded in it.

When I elevate a new version and create the next development
version, the entire "TO-DO" section gets cut and pasted into a
new record.