Re:Is “Investing in improving structure” better than “Paying...
by rumanator on Monday October 28, 2019 @09:00AM
(#21376484)
My take is that product managers care mostly about what functionalities were delivered and if the requirements are met. If the development teams deliver a quick and dirty solution and it meets some requirements then they check the requirement as delivered, and that's it.
When this happens then the devteam's negotiating position changes completely, because they are no longer arguing about how to allocate resources to deliver a functionality and instead they are asking to waste time rewriting something that was was already delivered and is supposed to be up and running.
Re:Is “Investing in improving structure” better than “Paying...
by pytester on Monday October 28, 2019 @11:45AM
(#21377959)
Do you not consider overall product quality to be a product decision?
Re:Is “Investing in improving structure” better than “Paying...
by Normal_gaussian on Monday October 28, 2019 @08:40AM
(#21376311)
Quality is so ridiculously subjective that I'm not sure a non-technical manager should approach the question, and a technical manager should refuse a direct answer and steer the conversation towards structure and deliverables.
Re:Is “Investing in improving structure” better than “Paying...
by pytester on Monday October 28, 2019 @09:31AM
(#21376786)
% of time spent on refactoring is completely objective. Whether that results in quality is another matter, but it's a dial that a product manager has control over that (usually) has direct impact on the quality of the end product.
There are exceptions, of course, and I'm pretty happy to have worked with them, but in general about 90% of managers I've worked with have resisted my attempts to get them to be explicit about the level of quality that they want.