*Result*: Some Lessons Learned in Transitioning to OO Software Development.
*Further Information*
*The article focuses on the lessons which provide good tips for smoothly completing the transition to object-oriented software engineering (OOSE). The transition to OOSE is a mission with problems. The adoption of new paradigm creates fear and uncertainty: fear of getting it all wrong and uncertainty about the process to use. Organizations often begin OOSE projects without any software engineering process to use as a foundation. The software development plan (SDP) is one of the most critical documents: it plays an important role in any software development project and must be the first document produced. Software development processes map the abstract theories of the object-oriented (OO) technique into concrete and repeatable actions. Metrics provide a means of measuring process quality and identifying potential bottlenecks. Development teams or developers' attitudes and attributes are one of the major keys to success or failure of adapting the OO technology on the project.*