Requirements Management in Outsourced Projects |
||||||||||||||||||||||||||||||
|
|
Home > Articles >
Transitioning from an insourced IT organization to an IT organization that outsources the majority of the IT functions is an eye-opening experience. Many key functions of traditional insourced delivery are no longer persistent across the IT portfolio.
Project management, business analysis, software development and infrastructure development are initiated and concluded within the project lifecycle. In an insourced model, the business analysts, project managers and developers are retained for the next project in the portfolio queue. In an outsourced model, these resources leave at the end of the contract and move to the next client opportunity.
Understanding the impact of an outsourced staffing model to the requirements and the business analysis function has a modest learning curve for IT managers new to an outsourced model. This article highlights a few lessons learned to help future managers adjust easier to the managing requirements in an outsource model.
Lesson Learned No.
Please login/register to read the entire article.
sponsored announcements and special offers
Difficult for competitors to equal. EMA reviews IBM Rational's new quality & requirements management offerings. The verdict, "For companies seeking to improve ROI delivered by software projects,we believe Rational's value proposition is difficult to match."
Microsoft Project Conference 2000
Use WorkLenz PPM to Manage Agile Software Development
|
| ||||||||||||||||||||||||||||