Estimation

[Neil Wills]

At the eng lead level and to help planning roadmap features it would be good to have a field to capture those estimates, but not have the field visible for the team when we decompose the epic into stories, and use the story point field.

Is there a way to have a field visible and not visible depending on the user group?

[Bill Sheboy]

Hi @Neil Wills 

I could predict some unintended consequences of hiding such a field...

If the team knows this is their process (i.e. an engineering lead makes a high-level forecast prior to refinement by the rest of the team) why not just leave the field visible, as both an learning and conversation starter for improvement?

Kind regards,
Bill

[Neil Wills]

When we have had the high level estimates visible then it has the unintended consequences of influencing the teams estimation.  If the t-shirt was a XS, S, M the may be, and have been influenced by that estimate, when the work after decomposition may be XL, L at the end of the day they are going to do the work.

One workaround that I have considered is take the high level quarterly initiatives\epics and translating them into the roadmap dates for the quarter.  And when we have the decomposed epic and stories then show how estimates and teams estimates differed to learn for future planning.