What is the right approach to define shipping timelines?

How are timelines handled in your organization between product and engineering?

For the sake of argument, let’s assume product has proposed a quarter’s worth of priorities for the team: a handful of new features. There are decent product requirement docs, story maps, and mocks where applicable. And let’s ignore outside forces like shifting priorities, missed requirements, and so on.

How does engineering take and vet that proposal so they can say “yes” to the timelines with a reasonable level of comfort? Knowing nothing is perfect, but agreeing or pushing back in an informed way, not just a finger in the wind.

I’ll stress that I’m not looking to shift responsibility or point fingers. I’m interested in understanding what roles product and engineering each play in your process and how a quarterly roadmap is built collaboratively to achieve to at least a moderate level of accuracy.

This topic was automatically closed after 180 days. New replies are no longer allowed.