Plan for portfolio management

Assembla offers rudimentary portfolio management. While it is very basic at this time, planning ahead will allow you to use advanced features as we roll them out without having to do extra work on changing workspaces around and moving files.

Here are the basic rules for workspaces:

Keep the following in mind when creating workspaces to achieve the best results.

What teams are you migrating to Assembla?
If you are migrating Development (a department), create one workspace. If you have a PMO which has projects, you may want to consider breaking workspaces apart for reporting purposes. In general, only create one workspace for working on code.

How do you want to handle reporting?

Right now, you can create a Portfolio workspace for your company, have project managers subscribe their project to the portfolio, and then view a complete list of all projects from your portfolio.

Project managers provide weekly status reports to the portfolio manager, which display in the portfolio workspace. A portfolio can have members, and then be a member of a portfolio workspace.

What will you do with the workspace when the project ends?

Keep in mind that projects get finished (or shelved, canceled...). Departments have ongoing work. You may want to run the project and then keep the workspace (with all associated data in it) for the department to continue using.

For example:

Here is an example of a portfolio workspace:


 



Copyright © 2006–2008 by Assembla, LLC / Phone 1.781.328.2241 / E-mail: info@assembla.com