|
|
|
There is a good article about economical impact of outsourcing and what potential buyer should expect on Outsourcing.com web site.
I’ll quote that work conclusion:
- Can outsourcing yield a positive ROI? Yes
- Are the yields as high as we expected? Probably Not
- Should we expect some added costs? Expectedly so
- Will we need to realign our approaches? Definitely
- Should we expect that some changes will need to be made? Probably
Full text is available at www.outsourcing.com
|
|
|
|
|
Vague requirement documentation is most often reason of fail in software development projects. One cause of such requirement problems is the language we use when write our documents. Issues and background that are very evident for one person, can be completely new and different for another, so it is creatical to use Elaborative, not Restrictive language in requirement documentation.
An article of Mark Monteleone is a great illustration of how that problem appears and what can be done to avoid it. Must read to all business analyst and other people working with requirements
|
|
