On Mon, Feb 14, 2011 at 5:14 PM, Michael Lyons <[email protected]> wrote: > Depending on what exactly you mean by planning across projects, if you're > talking about setting up how the project is laid out as a template then > that's pretty straight forward. > > If you're talking about looking at your assigned tasks from all projects > then that's also easily done; particularly with the VS plugin.
I suppose what I'm asking for makes more sense in the context of the GreenHopper plugin (for JIRA) which lets you assign tasks to sprints inside a particular project (the planning board). Inside that you can see the hours assigned and so on; but it's useless in that it's only per-project, so if there is X amount of hours available, and you have 3 projects to "work on", you need to manage the hours manually. I.e. assign 20 hours to this one, 5 to that one and 8 to this other one. You can't see that you have so-and-so amount of time remaining, and on my task board I can't see what things I need to work on across everything; I can only see per-project. > Otherwise if you're meaning having a task span multiple projects then I'm > not sure what software will let you do that. I would personally create a > project and break it down through the feature set out into multiple projects > - it's a bit of a hack, but you still have your user stories then tasks > underneath them. > > I think that by having planning across projects your starting to step away > from agile/scrum as you're looking at dependencies then from what I gather, > although I could easily be wrong since I don't know the exact situation you > are talking about. > > Otherwise you can always write your own plugins for Target Process via it's > API to manage such a situation. -- Noon Silk http://dnoondt.wordpress.com/ (Noon Silk) | http://www.mirios.com.au:8081 > Fancy a quantum lunch? http://www.mirios.com.au:8081/index.php?title=Quantum_Lunch "Every morning when I wake up, I experience an exquisite joy — the joy of being this signature."
