Menu
Display Lessons Learned Submit a new Lessons Learned Provide feedback on this repository FAQs regarding this system Administration
Deailed Lessons Learned Data
Type Cautionary 
Lesson Learned Statement Transition to COTS products must take into account transition of Business Processes as well. 
Issue/Risk factor Not making appropriate changes to the business processes (and planning for the time to do that) will delay the user organization's acceptance of the system. 
Impact on cost unknown 
Impact on quality high 
Impact on schedule high 
Type of data qualitative 
Recommended action Plan for business process migration 
Comments/Story see text 
Life-cycle Phase Planning 
Recommended audience Project manager 
Aspect Business 
Object Process 
Type of system logistics 
Type of company defense 
Number of COTS per project several to many 
Type of COTS diverse 
Date Created 7/2/2003 
Date added 12/10/2003 
Name Tricia Oberndorf 
Organization SEI 
e-mail po@sei.cmu.edu 
Reference "COTS-Based Systems Lessons Learned Web Pages" (http://www.sei.cmu.edu/cbs/lessons/) 
Link docs/TransitionIssues.doc 
Feedback
FeedbackID IndicateUsefulness IndicateSupport IndicateContradiction
No records
Submit feedback on this lessons learned