Aggregate view of multiple projects

This is a terrific feature idea. We have slightly different needs for the same sort of thing:

Some projects are large enough to occupy a full team. Other times, we may have a team working on "rats and mice" for several clients. Each of those clients would have an individual project that might only have 2 or 3 stories in the current iteration. However, at the team level, we want to track a 2-week iteration made up of 5 or 6 little projects like this. Velocity and progress really only make sense at this "parent" level. Any given individual project will fluctuate wildly.

Note: This is different than Sean's described scenario, which sounds like a way to scale agile to multiple teams (scrum of scrums). My scenario focuses on a single team working multiple small projects. But the solution might be the same.

It would be ideal if you could create a "parent" project. This project may or may not allow its own stories, but the backlog and icebox would show all stories from its sub-projects. Maybe you could specify a relative priority for the sub-projects to establish ranking? Or, ideally, the stories would just get a parent-project ordering/priority unique from the child project. Thorny problem I guess.

The reason "project-tagging" in a single project won't work is because we potentially want clients looking at their project stories, without seeing other projects'/clients' stories.

Michael

We have the same need as Michael - teams working on multiple projects in parallel. Not all individuals are working on the same projects and our projects ebb and flow in velocity based on external factors. The difficulty for us is that a particular individual may be pretty consistent in velocity across all the work they do for an iteration but their focus may shift from different subsets of all the projects they are working on for the week. So the automatic adjustment of tasks to an iteration using per-project velocity never seems to match up with reality.

I too have a small working on multiple projects at the same time and need to be able to see a condensed view of everything my team is working on for a given iteration. A calendar view with releases for all projects would be nice too.

I have the same sort of scenario - small team; lots of concurrent projects. I like Michaels requests/ideas - I would love to seem them combined with my requests below:

We typically have many projects in the works. Right now it is easiest to put them all in one Pivotal project, but that ends up with a lot of cross-noise. I really need a mixture of things to manage dozens of simultaneous projects:

1) the main idea of this thread - a multi-project view that lets me display many projects at the same time - say at least 10 - with some ability to interact with them. (maybe move stories between projects ;) I know other people want that feature badly)

2) the ability to group projects together - possibly in an arbitrary hierarchy, but just one level of grouping would suffice for my foreseeable future needs.

3) the ability to define groups of users and assign access to any particular project or project-group to a given group of users.

Thinking more about it, in this future world of better support for multiple projects, I'd like to see a way to prioritize across multiple projects. I could see how this might be problematic to do at the story level, but I think all I need is the ability to prioritize projects - and for each dev to be able to see all their assigned stories grouped and sorted by project priority.

In fact, if you wanted to be really fancy - and super consistent, allow Projects to be treated as Stories within a "master project". I could see most the same functionality we currently have at the story level being very useful at the project level - prioritization, icebox, labels, comments, ownership, etc. Even momentum - would need a little thought, but it might be as simple as the sum of all momentum of all active projects. Points should be the sum of all points of non-iceboxed stories for that project. Tasks wouldn't make sense for the obvious reason that Stories would provide that role.

I'll mention again: the ability to move stories between projects is a must.

Same here: one team, multiple projects. You may also want to have a look at my topic: "http://community.pivotaltracker.com/p..." for some ideas around how this could be implemented in PT.