6 ms·
WRT to those hugely expensive projects: for a while I've thought the real secret about offshoring is that it's simply a cheaper way to fail. Since most project
by hga 14y ago
WRT to those hugely expensive projects: for a while I've thought the real secret about offshoring is that it's simply a cheaper way to fail. Since most projects fail (outright canceled, declared a victory when they aren't, or over budget and time and generally far from feature complete), a cheap way to pretend you're doing software development has its attractions.
As for methodologies, perhaps getting everyone to actually use one is the biggest problem; that's been my experience. I have myself found about 4 things that seem to work:
The project should have a specifications document of one or two pages, no matter how complex. This is to try to get everyone on the same page, as it were, it has goals and requirements, must do N transactions/second, must run on X, etc. As much what and as little how as possible.
Further project documentation efforts must factor in the Don't Repeat Yourself (DRY) principle, i.e. the code is the only truth, and attempts to duplicate it are going to get out of sync unless you work really hard at avoiding that.
From OOSE/RUP: do short ("several week", 2-4) iterations and get your complete software and systems stack into a "Hello, world!" end-to-end state very early in them.
Otherwise, yeah, I've read a lot about software engineering beginning within the first month or two I started programming in the fall of '77 (sic) and while I think there is such a thing, it's indeed not really engineering as we otherwise know it. There's something there, but you learn it as much by doing as by more formal methods (classes, reading books) and there's no substitute for a serious amount of experience.