Tasks with a Single Deliverable and Multiple Resource Deadlines

[JennTa]

Hi, I have a specific use-case issue that comes up frequently within our agency, and I'm wondering if anybody else runs into this issue too. If so, what's your solution? Here's the use case: If two people are working on the same deliverable, we create a single task for this deliverable, even though they may have different items they own in the deliverable and different deadlines. The reason we moved from a single task as opposed to multiple tasks is because it allows easier collaboration between the resources. There are times though when we need Resource A to complete their portion of the deliverable before Resource B. Resource A doesn't always realize this, and they rely on the actual due date, causing Resource B to have little time to complete their work or be late on the task. Specific example: Task: Create and Optimize Website Landing Page Content Resources: Editor and SEO Specialist Details: Editor must create website landing page content before SEO specialist optimizes If you deal with this within your organization, I'd love your thoughts! Jennifer Tanabe Director, Project Management Vertical Measures

[TerryHy]

To me, that would be two separate Tasks with a dependency: Task A = Create Website Landing Page Content (Editor) Task B = Optimize Website Landing Page Content (SEO Specialist), dependent on Task A The Editor needs to create the content and then once created, the SEO Specialist needs to optimize the content. Was there a particular reason why you did not want to separate out the Tasks like that? If collaboration is a factor, then maybe having a 'Concept Planning' Task with the Editor and the SEO Specialist first, before Task A and Task B so they are on the same page? Just a thought... Terry Hynd EBSCO Information Services

[JennTa]

Hi Terry, Thanks for your response. Yes, we did originally have two tasks with a dependency. The pain point internally was that the two resources couldn't collaborate on the document if they needed to chat back and forth (within WF updates). The other pain point is that once Resource A was done, they would upload the document to the task, and then a project manager would have to re-upload it to the next task so that Resource B could begin work. It didn't seem efficient or a good use of time for a project manager. Ultimately, there are pros and cons to both ways, I guess it's just which cons our internal resources are most willing to live with. Jenn Jennifer Tanabe Director, Project Management Vertical Measures

[VicAl]

Would it work to have a Parent Task (Summary Task), with these two tasks underneath? Then you could attach the document to the Parent Task? Vic Alejandro, PMP, CSM | IT | Sr. Technical Project Manager Denver Water | t: (303-628-7262) | c: (303-319-6473) "http://www.denverwater.org/"> http://www.denverwater.org INTEGRITY | VISION | PASSION | EXCELLENCE | RESPECT

[JennTa]

That's an idea we can investigate. Thanks for the feedback! Jennifer Tanabe Director, Project Management Vertical Measures

[BarryBu2]

My first thought was also a parent task. However, if you're also timesheeting you're then allowing both resources to put time to the parent task rather than their specific task. In general, team members hate timesheeting and tend to put their time to the highest level they can. Have you explored two tasks, assigning task 1 to Resource A and simply sharing (rather than assigning) the task with Resource B? A bit fiddly for the PM (and not that much of an improvement on manually sharing the document after it's uploaded) but it is an option. Barry Buchanan Work Management Australia