For example in an initiation phase, I might have directories for: The next set of directories are for deliverables. The first subdirectory is usually Planning which is for anything associated with Phase Planning. The next level down under phases is focused on particular activities within the phase. The second set of directories cover the phases. I firstly create a set of directories for these functions. Firstly, I ask myself what will span phases. I prefer the structure as a combination of the two options above. My Preferred Approach to Project Folder Structure For example, it for an ERP implementation, it might be Finance, Manufacturing, Sales etc. For larger projects, the top level may in fact be a business area. You have a phased top level with the next level devoted to functions. For example, Risks, Requirements, Scope, Change Control, Development. Organise by function so that the top directory level are functions.For example, you might have directories for Feasibility, Business Analysis, Design etc.
![create folder structure diagram software create folder structure diagram software](https://drawio-app.com/wp-content/uploads/2020/05/Folding-and-moving-trees-in-drawio.jpg)
Organise by phase so that each top directory is a phase.There is no right answer to this question. Incidentally, we changed the whole directory structure at the start of 2006 and migrated only half the files for Project X. You then find out the 2006 refers to the end date of the project rather than the start date which was 2005. You can put them down now.Īnother reason for having a common structure is that we are not subject to the warped mind of someone who decides the issue register should be at the bottom of a folder structure called L:\IT\Projects\Financial Projects\2006\First Quarter\Project X\Miscellaneous\Updates\Recent\IRĪfter you have clicked away for five minutes following every conceivable logic path to find the register, you do a search only to find nothing. Hands up those who have clicked down and down and down into subdirectories looking for a document and reached the end of the line only to find the file you were looking for was not there? By this time I assume you are sitting there with both hands in the air. If I am a new project manager and want to know what a BRS looks like, I can dive into other projects and quickly locate the BRS directory. If they can be easily located for each project, it makes life easier all round. Common documents like a business requirements statement get used as models for other projects.
![create folder structure diagram software create folder structure diagram software](https://www.softwareideas.net/i/DirectImage/1557/create-diagram-in-specific-folder.png)
In this ever converging world, things like individual Gantt charts get sucked up into project master plans. If they are familiar with a common structure, it is easier to file new things, and find old things. The first is partly the “neat and tidy” answer but it also has to do with reducing the learning for people who move between projects. There are a number of other reasons which I will outline. If the only reason you can think of is that it keeps things “neat and tidy” then I expect you have given it about as much thought as I had. Why do you need a Project Folder Structure
![create folder structure diagram software create folder structure diagram software](https://docs.alfresco.com/content-services/images/acs-6.1-enterprise-architecture-overview.png)
It may sound trivial but the more I thought about it, the more factors started to emerge. It was then I thought it was a suitable topic for a white paper. I checked Google and that was not much help either. The project file structures sort of grew organically. Like most project managers I have developed a number of structures but never given it much thought. I was recently asked to provide advice on a folder structure for projects in a large organisation.