Expand my Community achievements bar.

The Community Advisors application is now OPEN for the second class of 2024. Apply to become a part of this exclusive program!

Tracking subprojects that are part of other big projects and reporting on it

Avatar

Level 3
Hi, Most of our projects that are being tracked in Workfront needs to go through some kind of architectural/security reviews by separate group. The other group wants to track the effort that they are doing as separate projects as they want to report on everything they are working on. How is everyone tracking these kinds of projects? Are you tracking it as separate projects and using cross project predecessors or will it be good to track reviews of multiple projects as just one project and add tasks to it for each separate project and use cross project dependencies. I am just trying to understand the best practices. Thanks
Topics

Topics help categorize Community content and increase your ability to discover relevant content.

2 Replies

Avatar

Level 8
I'm not sure what is considered best practice. I guess it depends if the review work is included in the labour cost of the project. We have a project per team that is 'operational'. The leader of the team could put in a single 'architectural review' task that spans the year. With this approach the team leader would know how many hours per week / month / year are spent doing reviews, but not what particular project. You also couldn't say task 43 in my project can't start until the review is complete. You could put an architectural review task in each projects task and assign it. It would show on the team leaders calendar / team views, it would have dependencies (task 43 can't start until this is done) but the time logged against it would count in the project hours (and if billable and/or with a rate, count as cost). Personally, I'd go with this one. The hybrid is to create an achitectural review project, and have a task for each project you're reviewing. Costs (if any) are in this project (so you could even over-ride billing rates just for this), interdependencies can be created etc. You'd just need to make sure it's excluded from reports/views that are only interested in 'real' projects.

Avatar

Level 7
Yeah, I think there are many ways to do this, and it depends on what you want to get out of it (what you want to measure/report on). You say that, " The other group wants to track the effort that they are doing as separate projects as they want to report on everything they are working on." I'm not sure why you still couldn't put a task in each project and still get them a report on everything they are working on..