Trying to figure out the best way to create your projects in Central Desktop? As you know a workspace is an area inside of Central Desktop that you can use to manage a project (among many other things such as blogs, forums, intranets etc). I believe that the best way to manage projects within Central Desktop is to use the “Workspace = Project” layout.
Of course you can manage multiple projects within one workspace. However, using a Workspace to manage a single project has many benefits over managing multiple projects within a workspace. One of the first benefits you will realize is the depth of project management goes down an extra level and spreads out wider (allowing multiple milestones that can contain multiple task lists).
Instead of this scenario (Multiple project within a workspace)
- Workspace Group(s) = (examples: Departments, Clients, Intranets)
- > Workspace(s) = Department
- > > Milestone(s) = Project
- > > > Task List(s) = Larger Project Goals
- > > > > Tasks = Individual Deliver-ables
you would have (Workspace = Project):
- Workspace Group(s) = (examples: Client Projects, Engineering Projects)
- > Workspace(s) = Overall Project
- > > Milestone(s) = Larger Project Goal or Deadline
- > > > Task List(s) = Group of Individual Deliver-ables
- > > > > Tasks = Individual Deliver-ables
This allows you to segment your projects into their own areas allowing you deeper granularity when it comes to membership and permissions. This means you do not have to worry about External Users such as Clients seeing each others projects and also keeps the noise level down for those that might really only be part of one or two projects. It will keep your project calendars less cluttered and allow more control over incoming information with Workspace Digest Emails and Recent Activity lists.
You will also experience more granularity with Usage, User, Task, Milestone, Time Tracking and Activity reporting since this can be done at the project level. This makes isolating information much easier than it would be if you were using a workspace to manage multiple projects. You will also be able to track project properties such as start/end dates, owner, primary resource, beneficiary, status, priority, risk and comments. On the Enterprise and Community Editions you can create your own custom project properties using Workspace Field Extensions.
You can also take advantage of Workspace Backups and Archiving of Workspaces (Projects) at a more granular level. And on the Enterprise or Community Edition accounts you can also take advantage of the Shared Folders option to keep yourself from having to upload the same documents into many different workspaces when using this method.
Using the Search Engine, Tagging, Status Filters and Document Filters will become much more targeted this way as well.
I hope this is useful information for those that are trying to decide which way they want to set up projects. Remember, your users will only see workspaces they belong to. So if you end up with 50, 100 or 200 workspaces because you have that many projects – if you use Workspace Groups, Member Groups and Custom Reports in the Project Reports area – this will be a breeze. (I will talk more about those areas in my next post.)
To review and give you an example of this in action:
The hierarchy works as such:
Central Desktop Account
> Workspace Group
>> Workspace (project)
>>>Milestone (larger project goals)
>>>>Task List (grouped deliverables)
>>>>>Tasks (individual deliverables)
a deeper layout would be as such:
Central Desktop Account
> Workspace Group 1 (example: Client Projects)
>> Workspace 1 (example: ABC Company Deployment)
>>>Milestone 1 (example: Phase 1 rollout)
>>>>Task List 1 (example: Post Sales Check Points)
>>>>>Task 1 (example: Review and Authorize Client Contract)
>>>>>Task 2 (example: Review and Authorize Client Scope of Work)
>>>>Task List 2 (example: Pre-Developement Check Points)
>>>>>Task 1 (example: Complete Needs Assessment Form)
>>>>>Task 2 (example: Review Needs Assessment Form)
>>>>>Task 3 (example: Complete Pre-Development Form)
>>>>>Task 4 (example: Review Pre-Development Form)
>>>Milestone 2 (example: Phase 2 Rollout)
>>>>Task List 1 (example: Post Development Check Points)
>>>>>Task 1 (example: Review and Authorize Needs Assessment Form)
>>>>>Task 2 (example: Review and Authorize Pre-Development Form)
>>>>Task List 2 (example: Development Check Points)
>>>>>Task 1 (example: Draft Development Plans)
>>>>>Task 2 (example: Review Development Plans)
>>>>>Task 3 (example: Create Roadmap)
etc. etc. Having as Many Milestones that contain as many Task Lists that contain as many Tasks as you require.
>> Workspace 2 (example: DEF Company Deployment)
>>>Milestone 1 (example: Phase 1 rollout)
>>>>Task List 1 (example: Post Sales Check Points)
>>>>>Task 1 (example: Review and Authorize Client Contract)
>>>>>Task 2 (example: Review and Authorize Client Scope of Work)
>>>>Task List 2 (example: Pre-Developement Check Points)
>>>>>Task 1 (example: Complete Needs Assessment Form)
>>>>>Task 2 (example: Review Needs Assessment Form)
>>>>>Task 3 (example: Complete Pre-Development Form)
>>>>>Task 4 (example: Review Pre-Development Form)
>>>Milestone 2 (example: Phase 2 Rollout)
>>>>Task List 1 (example: Post Development Check Points)
>>>>>Task 1 (example: Review and Authorize Needs Assessment Form)
>>>>>Task 2 (example: Review and Authorize Pre-Development Form)
>>>>Task List 2 (example: Development Check Points)
>>>>>Task 1 (example: Draft Development Plans)
>>>>>Task 2 (example: Review Development Plans)
>>>>>Task 3 (example: Create Roadmap)
etc. etc. Having as Many Milestones that contain as many Task Lists that contain as many Tasks as you require.
etc. Having as many Workspaces as you require or your account is set up for. Remember the the Enterprise Edition allows for an unlimited amount of workspaces.