Organization
Organization Name: BABEL SISTEMAS DE INFORMACIÓN, S. L.
Organizational Unit: Remote Applications Development and Maintenance Projects
Appraisal Sponsor Name: Eduardo Martín
Lead Appraiser Name: Ramiro Carballo
Partner Name: Caelum Information & Quality Technologies, S.L.

Organizational Unit Description
Basic Units / Support Functions:
DIGIFIN
    Mexico City, Mexico State Mexico
Mediators Web Portal (SANITAS)
    Madrid, Madrid Spain
Human Resources SFG
    Madrid, Madrid Spain
    Mexico City, Mexico State Mexico
    Mairena de Aljarafe, Seville Spain
    Barcelona, Barcelona Spain
    Lisbon, Great Lisbon Portugal
    Casablanca, Casablanca-Settat Morocco
SCORE CARD
    Mairena de Aljarafe, Seville Spain
Quality Assurance SFG
    Madrid, Madrid Spain

Organizational Sample Size
% of people included: 39
% of projects/units included: 10
Org Scope Description: 2 Traditional Development projects
1 Agile Development projects
2 Support Groups: Quality Assurance SFG and Human Resources SFG

Appraisal Description
Last Day of Appraisal Onsite: Apr 28, 2017
Appraisal Expiration Date: Apr 28, 2020
Appraisal Method Used: SCAMPI V1.3 A
Model Information: CMMI-DEV v1.3
Sampling Summary
Sampling Factors: Location (Not Relevant: Not Relevant: There are three locations in this OU. Madrid, Seville and México are the centers of software development inside of BABEL. The people in these centers are integrated in several teams. CUBO Methodology is used in the three development sites. So, location is not a determining or distinguishing factor affecting the implementation or performance of work.)

Customer (Not Relevant: Not Relevant: All projects are executed in the Development & Maintenance Centers. All projects follow CUBO Methodology. In the case a customer require using a different method, this project should be rejected by the Centers Manager. So, customer is not a determining or distinguishing factor affecting the implementation or performance of work.)

Size: Relevant: Work is performed differently based on the size of the software projects or the maintenance requests. Minor changes are managed as corrective or maintenance activities in the software maintenance service, while others are considered enhances and evolving projects.

Organizational Structure (Not Relevant: Not Relevant: All projects inside the Development use CUBO Methodology. These centers are inside the Operations Department of BABEL. So, organizational structure is not a determining or distinguishing factor affecting the implementation or performance of work.)

Type of Work: Relevant: Type of work is a determining or distinguishing factor affecting the implementation or performance of work, considering the following types of work: software development, maintenance services and professional services.

Lifecycle: Relevant: Life Cycle is a determining or distinguishing factor affecting the implementation or performance of work (Type of Life Cycle used in the project.)

Sampling Factor Values: Small (Size): Small changes are requested to solve little problems inside a software maintenance service. A request is considered small if the estimated duration is less than 100 hours.

Large (Size): A set of product features or large change requests are the base of software development or maintenance projects, developed by request of the customer. The estimated duration is more than 100 hours

Software Development (Type of Work): Set of tasks to build a software product during an established time.

Maintenance Services (Type of Work): A service to manage the delivery of a set of change requests over an existing software product.

Professional Services (Type of Work): Time and material service based in skills categories.

Agile (Lifecycle): Project management method is based in SCRUM or other kind of agile practices.

Traditional (Lifecycle): Project management activities are based in traditional methodologies.

Subgroups:
Agile Development Projects: Software projects managed with SCRUM or other kind of agile practices.
26 People, 6 Basic Units
- Large
- Software Development
- Agile

Traditional Development projects.: New development software projects and software maintenance requests which are estimated in more than 100 hours of effort.
50 People, 25 Basic Units
- Traditional
- Software Development
- Large

Model Scope and Appraisal Ratings
CMMI-DEV v1.3
Level 2 Level 3 Level 4 Level 5
REQM
PP
PMC
SAM
MA
PPQA
CM
RD
TS
PI
VER
VAL
OPF
OPD
OT
IPM
RSKM
DAR
OPP
QPM
OPM
CAR
Maturity Level:Maturity Level 3