A
anovak
OK...here goes. We have several development teams that keep track of
anywhere from 30-100+ projects in their respective areas. Some are a
week long, some are 6 months long, some are a year long, some are a
couple of days long...you get the picture. Some are large enough that
they may require hefty work breakdown structures. Some not. Probably
most not.
These things are out on indivdiual spreadsheets per group. My initial
thought is in order to keep things reportable witin the PWA, all these
items on their project list need to be treated as project objects in
the database (complete with custom fields for things such as
"magnitude", "need", "risk", etc.). Then organize them with outline
codes.
However, keeping all these things updated could be pretty tedious vs.
the spreadsheet (especially those that don't need a WBS -- open
project, open project information, update fields, close project, open
next project, etc.). No filling down, right, etc.
Is this the way to do it or what would be a practical way to manage
these projects as tasks within multiple "Development Team X" projects?
and STILL allow the executives to see the status of ALL PROJECTS on a
single list?
Hope I'm making sense. Any insight would greatly be appreciated.
Thanks,
Andy Novak
University of North Texas
anywhere from 30-100+ projects in their respective areas. Some are a
week long, some are 6 months long, some are a year long, some are a
couple of days long...you get the picture. Some are large enough that
they may require hefty work breakdown structures. Some not. Probably
most not.
These things are out on indivdiual spreadsheets per group. My initial
thought is in order to keep things reportable witin the PWA, all these
items on their project list need to be treated as project objects in
the database (complete with custom fields for things such as
"magnitude", "need", "risk", etc.). Then organize them with outline
codes.
However, keeping all these things updated could be pretty tedious vs.
the spreadsheet (especially those that don't need a WBS -- open
project, open project information, update fields, close project, open
next project, etc.). No filling down, right, etc.
Is this the way to do it or what would be a practical way to manage
these projects as tasks within multiple "Development Team X" projects?
and STILL allow the executives to see the status of ALL PROJECTS on a
single list?
Hope I'm making sense. Any insight would greatly be appreciated.
Thanks,
Andy Novak
University of North Texas