For example, how come you didn't spot the architectural flaw earlier? Do you normally wait 'till the code comes back to review the architecture? That's the kind of hacker methodology we used back in the 80's.
Me, I'm used to more modern methodologies which include up-front review and sign-off of level I, II and III architecture, at least! Don't you?
No John, because architectures at the misc. tier levels are the responsibility of the design team. It is at the tech spec level, not the functional spec.
And if my team here, which includes visionary folks and customer facing people and those sorts, has to review *every single technical design decision*, like even something as basic as the field level data model (tedium-city), then there is no point outsourcing. This is where the real value in development lies, John.
If no design decisions of any kind can be done offshore, such as this sort of thing, then what is left to the "development process"? Typing only I would say. If the team here writes a spec that a monkey can code, you could probably hire a secretary to type it in for as much as the indian teams cost. And then you have no piracy or timing issues. |
