|
|
|
|
|
by mst
6088 days ago
|
|
Development of the codebase might not have been but development of the product clearly was. And the use cases. And the commercial viability of the market so their company had a chance to be around to support their customers. And the business understanding needed to support those customers properly. Not all development is programming. |
|
The hair-splitting begins. The phrase "software development" in my book, and I suspect in most people's, implies code. If you just mean any old development, well, sure, the customer development was proceeding quite nicely. Maybe that was what they meant?
Try a simple thought experiment. If the customers learned that there was no code and the product consisted of nothing more than the printed "screenshots" they'd been shown, would they care? I'd guess that one's answer to that is pretty correlated with whether or not one thinks deception was involved here. My answer - not about these particular customers, but in general - is yes, they would care. As a customer, I certainly would. (Not, of course, because of any objection to paper prototyping as such, but because a critical piece of the situation had been hidden from me.)