Number of developer hours should be nearly nothing. A couple per week. Done properly, these things should keep you from getting halfway into implementing somet

Number of developer hours should be nearly nothing. A couple per week. Done properly, these things should keep you from getting halfway into implementing something, having a question nobody thought of, and getting stuck. Then stashing your work and moving on to something else while the original feature lingers half-done or dies altogether, either way the timeline got blown. This is only possible (the time savings I mean) if you have a PM or product owner -- making devs do that work is madness.