How do folks handle tracking changes to Project start & Project target dates on JPD?

[Sonia Bramwell]

Hi all!

Our Strategy team is pushing to measure "% on-time roadmap idea completion". 

As part of this methodology, they'd like for Product to introduce something like a "locked in" date -- the original date(s) set for an idea on JPD (at minimum just Project target or a Start & Target pair).    

Is anyone else out there doing / providing this to your org?  Or do you just change Target (and/or Start) dates as you get more info (from Tech / other stakeholders) and present only the mostly recently updated date(s)?   Any other practices (checkpoints / notifications etc)  around shifting roadmap dates would be very helpful to hear about -- even if dedicated JPD fields for something like "locked in" or "original" dates aren't being used.  Anything that helps track % roadmap completed would be great to hear about.    

Your approaches / best  practices highly appreciated!  

[Tanguy Crusson · Accepted solution]

Hi @Sonia Bramwell , at Atlassian we do use Atlas for that

Basically when we work on something bigg-ish, we create a project in Atlas. People can subscribe to this project. Every week we send a short (280 character) update about the project with a status (on track, off track, at risk) for a target date (day, month, or quarter)

And we show these statuses in our JPD ideas via the Atlas <> JPD integration

[Sonia Bramwell]

Thanks for this @Tanguy Crusson -- Atlas has been on my list to check out.  Do you have any docs / info on the Atlas & JPD integration:  what it enables, what's best / mostly commonly done in which product / what's the primary function of each?

Thanks! 

[Tanguy Crusson]

Yep - from the FAQ: 

How do I use Jira Product Discovery with Goals and Projects (ex Atlas)?

Here is a demo for how to use Atlas goals and projects in Jira Product Discovery

[Gary Spross]

We're not doing anything like this, but I would think the most straight forward way would be to create fields to store the original dates and then utilize automation to populate those fields based on the initial setting of the Target Start & Target End date fields. The automation would look to see if the corresponding original date field is empty first. If not, then don't update it. This way subsequent updates to the Target Start & Target End date fields wouldn't affect the values contained in the "original" date fields.

[Sonia Bramwell]

Brilliant Gary, I like that...  Thanks a ton!

Would still love to know if anyone is tracking this at all, and/or how you're informing stakeholders when roadmap dates shift.

Thanks again