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 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. We are but the stewards of their data.I was recently asked to provide advice on a folder structure for projects in a large organisation. Ultimately, the system works as it should. In these cases, upper management has been on board from the beginning to back us up on enforcing a more logical organization structure, but only for those types of projects. The only caveat to the above has been when we've won certain projects that have alphabet regulations attached to them requiring tightly-controlled and audited access, etc. The whole process has also taught us in IT to learn that, like learning styles, everyone has an organization method that works for them and ultimately, these people are the ones bringing in the big $ that keeps all of us happily employed. We've had many go-rounds on this over the years, but we've also observed some progress on cleaning up the mess.
You want an intern to have rights to "S:\project\01Widgets\Gearbox\Catpictures\New Folder(2)\ResearchTask4" but not to "S:\project\01Widgets\Confidential Financial Information"? Sorry, they get the entirety of "S:\project\01Widgets" and it's the department manager's problem to decide if a)the intern is trustworthy enough to have privileges to the entire project or b)the folder gets cleaned up in a more logical pattern. Then, in the departmental "root" folders, we only assign permissions to the top levels. Our solution to this nightmare was to, naturally, lock down the root folders and not allow new ones unless a entirely new, funded department came along. The same wonderful file "organization" has persisted and it always will persist. When I came on, I rolled all of the random file servers that had cropped up into one "S drive" server and provided semi-departmental top levels. Some folks have worked here the entire time. We have an "S: drive" which has been around since the late 80s when our organization was born and started running its own file server. Your file structure examples(both) look quite familiar. As several above me have already mentioned, it's not IT's problem to solve nor is it even IT's prerogative.
0 kommentar(er)
