You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
In our team, sometimes we ship things between locations. I need the item to reach the destination before I can start working on tasks that involve that item (i.e. waiting for a circuit board to be delivered).
If I know delivery will take about 5 days, then I don't want any of the blocked tasks to start until 5 days from now. If the item DOES get delivered early, or there's a delay in delivery, I want to be able to see the effect of that.
I thought about setting up a "release" for when the item arrives. But then how do I dynamically control the beginning of work on the following release to coincide with the end of the current one? Otherwise I can set up a task for "waiting for delivery", however, this throws off the scheduler, because then I have a team member literally waiting around for a delivery rather than doing some other work in the meantime.
How do I make this work in Portfolio?
To all future internet people, I found an answer but only in the Portfolio Server documentation. This will work great!
Just in case that link goes dead, you are able to add an "Earliest Start Date" for an issue. So you either modify the "earliest start date" of whatever is being blocked, OR you can create a task for "delivery" and set its estimated time to 0 and adjust the "earliest start date" for it as you learn more about when it will arrive to have everything else schedule as portfolio does.