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 Microsoft Projects, there's the concept of a Tracking Gantt Chart that allows you to see the difference between your initial plan and your actual accomplishments. It's a clear indicator of schedule slip.
Is that possible in Advanced Roadmaps? This is an adoption blocker for us.
Hi @Nick Sweet,
Your question is all about baselining. The baseline is something that was available in Portfolio 2.x but not in the new planning experience.
Advanced Roadmaps has a different approach to schedule slip. This is all over the place in the on track / off track status indicators on the release page. It is available through the alerts in the top right corner of your screen. It is available in the color coding of the roadmap timelines (issues with a problem are highlighted with a yellow color). I personally think they are much more helpful than comparing with the baseline to indicate there's a problem with your plan.
Nevertheless, you can definitely add baselining functionality to your plan by adding custom fields for baseline start and baseline end dates, where you can then store the baseline start and end dates. The graphical visualisation of that baseline is currently missing, but you would be able to show the baseline dates in the fields section of your plan, while the actual plan is displayed next to it.
If you'd like, you can watch and vote for suggestion JSWCLOUD-20495 about enhancing this capability.
Thanks -- that's a great answer!
I think the intent is to use schedule slip to inform future planning. Though, for a scum-based team, I think that tends to be covered at a sprint level. I don't know how I'd track that for a kanban-style team apart from baselining -- do you have any recommendations?