How to handle large multiteam/multiphase IT programs in Product Discovery

hroy

We are trying to use Product Discovery to capture teams impacted at the Product Discovery stage, but we are realizing that we would need more Product Discovery tickets as the feature elaborates. Is there any learning from other customers that we can reuse here to keep a reign on the number of Product discovery tickets that we might end up creating for 1 value statement. We dont want to recreate our Jira in Product Discovery as well. Any guidelines of creating Product Discovery tickets that we can reuse? pls help. thanks 

Adrian.Lester

Whenever we identify that some work is best achieved by delivering in multi-phase / iteratively we create 1 idea per phase/iteration (usually clone the original).  This lets us move each phase independently, and helps keep Jira clean and uncluttered with 'future stuff'.

 

The multi-team thing we handle by linking multiple delivery tickets (across the various teams) to avoid recreating Jira in JPD.