project management

[Olaf Doschke]

I have a pretty good understanding on how to organize a foxpro project in folders and subfolders of eg libs, graphics, etc. But this is just a small part of the overall repositiory of files belonging to a prject, including administration, correspondence, design, documentation, etc. I'm currently rethinking the folder structure to better support an agile software development flow, no matter if that's called SCRUM or something else.

I'm looking for inspiration here: How do you organize all your files regarding a customer's project and/or product? What would you think is an ideal repository of administration, correspondance, design, implementation and documentation files?

To start with, this is the current folder structure we used in a larger project - without going into details about the subfolder structure:

-Administration
-Acquisition
-Requirements
-Backend
-Design
-Documentation
-Bug Reports
-Frontend
-Graphics
-Web (publishing)
-Correspondence
-Side projects
-Quality Assurance
-Releases
-Testdata
-Templates
-Third Party Software
-Miscellaneous

Some ideas as a starter:

1. The Frontend folder, is where the foxpro project(s) reside, and eg the Graphics folder could rather go in there instead of being at this level, it could also go up to even a more common folder with a repository of graphics for all projects.

2. The Miscellaneous folder should be removed and each file in there should have it's home folder where it belongs to.

3. Backend and Testdata is quite the same and should be merges, then Frontend and Backend together make up the implementation and should be put into a new folder Sources or Implementation.

Now I'm looking forward on your ideas, oppinions, recommendations.

Bye, Olaf.