Organization
Organization Name: Bilbomática
Organizational Unit: e-Government Area within Bilbao office
Appraisal Sponsor Name: Walter Mattheus
Lead Appraiser Name: Giuseppe Satriani
Partner Name: ESI - European Software Institute (Tecnalia)

Organizational Unit Description
Basic Units / Support Functions:
ESTSDI01
    Bilbao, Vizcaya Spain
ANSKON19
    Bilbao, Vizcaya Spain
Quality Group
    Bilbao, Vizcaya Spain
WL11MED
    Bilbao, Vizcaya Spain
SALUDPRE
    Bilbao, Vizcaya Spain
EDA15
    Bilbao, Vizcaya Spain
EASME01
    Bilbao, Vizcaya Spain
Operation and Human Resource Management
    Bilbao, Vizcaya Spain

Organizational Sample Size
% of people included: 22
% of projects/units included: 13
Org Scope Description: 6 out of 45 development and maintenance projects executed within e-government area and the associated Support Functions (2): Operation&Training and Quality Team have been selected as a representative sample.

Appraisal Description
Last Day of Appraisal Onsite: Jul 16, 2020
Appraisal Expiration Date: Jul 16, 2023
Appraisal Method Used: SCAMPI V1.3 A
Model Information: CMMI-DEV v1.3
Sampling Summary
Sampling Factors: Location (Not Relevant: Bilbao is the only office under the assessment scope)

Customer (Not Relevant: Not relevant because independently from the customer, all the projects are managed by using Bilbometodo that maps any specific adaptation of any customer)

Size (Not Relevant: Bilbometodo contains some tailoring for small and big projects that do not affect the homogeneity in project execution.)

Organizational Structure (Not Relevant: Not relevant because we arespeaking about one specific area very well defined: e-Government Area within Bilbao office)

Type of Work: Two different types of projects are managed within the OU: Development Projects and Maintenance Projects (normally managed by using a “bag of hours” type of contract

Methodology: Even if a map between agile methods and Bilbometodo exists, the sponsor asks for having a specific focus on projects using agile methodology

Sampling Factor Values: Development (Type of Work): New applications development

Maintenance (Type of Work): Application maintenance managed by "a bag of days" type of contract

Traditional (Methodology): Projects managed by a traditional waterfall life-cycle

Agile (Methodology): Projects managed by using the SCRUM method

Subgroups:
Development Traditional: Development projects managed by using a traditional methodology
29 People, 7 Basic Units
- Development
- Traditional

Development Agile: Development projects managed by using an agile methodology (SCRUM)
25 People, 5 Basic Units
- Agile
- Development

Maintenance Traditional: Maintenance projects managed by using a traditional methodology
78 People, 17 Basic Units
- Maintenance
- Traditional

Maintenance Agile: Maintenance projects managed by using an agile methodology (SCRUM)
63 People, 16 Basic Units
- Agile
- Maintenance

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