3 ms·
It seems like the fundamental problem for the scenario presented in the article was an inability of the customer to communicate their strategy and a completely
by brigadier132 3y ago
It seems like the fundamental problem for the scenario presented in the article was an inability of the customer to communicate their strategy and a completely hands off approach during implementation when they should have had at the very least biweekly checkins with developers with pre-negotiated milestones.
- dagmx 3y agoYes, I agree. This is fundamentally a communication issue not a “developers run amok” issue to me. They shouldn’t be checking in after two months. They should have regular check ins. They shouldn’t have had such a vague brief. They should have discussed a wide range of off the shelf options from the get go to see if they needed something bespoke or not.
- roncesvalles 3y agoThe fundamental problem is that a non-technical person has specced out a technical product without input from technical people. A restauranteur wouldn't develop a menu without input from a chef or prior experience as one. A layperson wouldn't design a real building without input from an architect or engineer. Yet for some reason a myriad of non-technical people (read: laypeople) feel empowered to design, spec, and strategize about software. It still boggles my mind that "product management" is a real profession.