With the introduction of the new BizDev Support Engineer, there doesn’t seem to be much use of the discovery duty role. As the BizDev support engineer is part of the discussion from the start, it would reduce any context switching if the same person were to do the initial high-level discovery (upto 5 hours). Any deeper technical discovery we were anyway scheduling for in the upcoming sprint. The only change would be that the deeper technical discovery would be assigned to someone on the team who has the capacity to take on a new epic.
@team What are your thoughts on this? Does anyone see any benefits to keeping the discovery duty role in addition to the bizdev support engineer?
PR to remove the discovery duty role is here if anyone would like to review.
Note: Last date to review the PR and this post will be 22 August 2025.
The DD role has a secondary function, which is making it clear who is available to take on a new project. I’d sooner rescope the DD role rather than remove it-- if we’re no longer requiring someone to allocate that time on a rotation, we still need to know who would be the point person to assign these discoveries to, and an easy way to determine that.
Currently, when I need to check who to send discovery work to, I look at this spreadsheet and check whose name is in the “Bebop DD” column for the sprint (there might be an easier way to do this, but I’m not sure what it is!)
@pooja If the BizDev Support Engineer takes over the discovery duties, which would be the easiest way to find out who they are so I know who to send discovery work to?
EDIT:
Apologies if this is covered in the PR; I only noticed the link after posting, and haven’t had the chance to review it.
@Ali If it’s a high level discovery then the BizDev Support Engineer is expected to take it (provided they have the capacity). Otherwise the role statistics spreadsheet (which is being kept up-to-date by epic planning managers) tracks who has the capacity to take on new epics, so you could send it to them.