Product Operations Program ManagerBarcelona, Cataluña, Spain
Not with respect to the project content, but to the project governance. Do you always use the same folder structure or do you customize it on a project basis? Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I totally agree with Peter. Level 1 & 2, are mostly generic and then it starts getting more specific to the project and requirements. Saving Changes...
It really depends on what information is required to support governance and how it is stored. If you are using a collaborative environment with powerful search capabilities (e.g. a Wiki), you might go with less of an imposed structure. If teams are using standalone project documents, then a standard folder structure for critical ones (e.g. schedule, RAID log, charter) is advisable.
One approach I've seen is a single folder per project (top-level) where they approved & current versions of the key artifacts are stored, and then a separate (unique by project) structure for where the work is actually done. That way, governance analysts can view the "must haves" easily, but team members can create stuff according to their personal preferences.
Kiron Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
In the organization where I am working today we have a defined process related to governance. And audit people have KPIs defined related to the process. So, the folder structure matchs the process steps. Saving Changes...
Community Champion
