5 ms·
Is this suggesting that all tickets should be fully scoped and planned by Product? If so, no. Devs also need to contribute to planning and should be able to wr
by interbased 3y ago
Is this suggesting that all tickets should be fully scoped and planned by Product? If so, no. Devs also need to contribute to planning and should be able to write their own tickets when it’s needed. They have context that is necessary in order for planning to be done properly.
- pavel_lishin 3y agoWe had this happen recently. We needed a feature implemented, EMERGENCY PRONTO ERMARGERD. ~15 tickets came down from On High. Half of them were effectively lists of things required for launch, the other half were individual "we must change this page", and one was basically "implement the feature" - and we were asked to scope it. This was for a system that none of us have had any recent (2 years) experience working in, in a language that most of us weren't familiar in, and dealing with payments. No, I'm sorry, I cannot scope this vague "make thing work" ticket that looks like foam in the sea of requirements, the one that we're actually going to be spending 90% of our time working on, that needs to be investigated and broken down into individual tickets later on.