(no title)
wnmurphy | 1 year ago
When product tries to design the solution, tosses it over the fence, and engineers who don't know any better just implement it, you end up with a codebase that consists of parts duct-taped onto the side of other parts. Over time this compounds the cost of future development.
When you let engineering design the solution, they design for reuse, with the lightest touch. This decreases the cost of future development by keeping the codebase maintainable, understandable, unsurprising, simple, etc.
If your user stories from product contain implementation details, you need to guide the discussion back to the actual problem that needs to be solved.
fmbb|1 year ago