Re:Dear Client, Here’s Why That Change Took So Long
by dkarl on Wednesday May 08, 2019 @06:49AM
(#19857608)
It sounds like you're only selecting jobs that require the approach you're accustomed to, which is fine when you get to pick your jobs, but it isn't an option for internal dev teams that work on a product. The jobs come at whatever size they are. If the job is to change a word on a web page, there isn't going to be an architecture diagram, and UAT is going to mean someone reloaded the page and messaged "looks good, thanks!" to the developer.
For a consumer product with millions of users, there's probably a checklist of device platforms, screen sizes, browsers, and screen orientations to check that one-word change, but for a SaaS offering with less than 100k users, probably not.
That is why any proper RFP answer already provides a broad overview how the problem would be tackled, and possible solutions to the described problem.
Also why during the project development, at various delivery phases, artifacts like architecture diagrams, documentation and UAT from customer team take place.