Earned Scope Management (ESM)Application in México

Dr. Francisco Valdés-Souto Associate ProfessorDepartment of Mathematics,Science Faculty,National Autonomous University of Mexico (UNAM)fvaldes@Ciencias.unam.mx

CHAIRMAN COSMIC Practices Committee

Mexican Software Metrics Association (AMMS)Founder AMMS

2

AGENDA

COSMIC IN MEXICO

SOFTWARE PROJECT SCOPE IMPORTANCE

EARNED SCOPE MANAGEMENT (ESM).

CONCLUSIONS

01

02

03

04

01

02

03

04

05

06

2006The ISO/IEC 19761 is

adopted as National

Standard NMX-I-119-NYCE-

2006

2008 - 2009The first person in Mexico get the COSMIC certificate.

The first company specialized in software

measurement and estimation in Mexico is launched. 2014COSMIC is included in the General Application

Administrative Manual on Information Technology and

Information Security (MAAGTICSI), which makes its

application "mandatory" for Federal Government entities

in Mexico.

The number of COSMIC certificate holders increase

2015The first National Congress of Measurement and Estimation of

Software (CNMES15) is held, focused on COSMIC method.

A colloquium is held at government level to establish the strategy

to promote the development of software until 2024. A specific line

of action related to COSMIC is determined: "DETERMINATION OF

BASIC, TRANSVERSAL AND TRANSCENDENT METRICS“.

The Mexican Association of Software Metrics (AMMS) is created.

The first call is launched to collect information and develop the

Productivity and Cost Baseline Study of the Mexican Software

Development Industry.2017

It is documented the first successful

adoption of COSMIC in the government,

which wins an award from a magazine

focused on digital government. However,

some poor adoptions of COSMIC are

identified.

The preliminary results about

Productivity and Cost Baseline Study

were presented at CNMES17

2018The Productivity and Cost Baseline Study of the

Mexican Software Development Industry is

released and printed.

The third CNMES is held joint with the

ITCONFIDENCE from ISBSG

COSMIC in México

3

4

COSMIC Certificate Holders in Mexico

5

Issues in Adoption

MISING AUTHORITYThere was no authority or national

reference that could determine

whether the results obtained from the

COSMIC application were correct or

not.

IT IS NOT MAGICSimilar to CMMI evaluation, the people

think that getting the Certificate they

automatically will get all the

knowledge needed to implement

COSMIC, using it for estimate and

control software projects!

EASY WAYThe government entities focused on

request certified people as a requisite

in the bids, not experienced in the

implementation of COSMIC.

This caused many problems because

they knew how to measure only but

not how to use these measurements.

Bad results!

2006 -

2018

6

Estimation the main use of COSMIC

Strategic Vision of Use of COSMIC

Frank Vogelezang, 1er Congreso Nacional de Medición y Estimación de Software, México 2015

The software estimate with COSMIC it is enough?

Is it enough to have an accurate estimation model?

01

02

7

An Analogy…

§ 2 years of baccalaureate courses

§ Approximate 35 weeks of going to school

§ 175 days of round trip

§ $15 USD each day for the trip -> $75 each week

§ 90 minutes each day for the trip

  Monday Wensday Tuesday Thursday Friday

Regular day

Cost [$] 15 15 15 15 15Acum[$] 15 30 45 60 75Time [min] 90 90 90 90 90Acum[min] 90 180 270 360 450Distance [KM] 10 10 10 10 10Acum [Km] 10 20 30 40 50

Specific day

Cost [$] 20 15 25 15 15

Acum[$] 20 35 60 75 90

Time [min] 120 90 150 90 90

Acum[min] 120 210 360 450 540Distance [Km] 10 10 10 10 10

Acum [Km} 10 20 30 40 50

8

Software Project Execution: Risk

Project End

9

Software Project Scope Importance

01

02

03

Lack of ApproachesO´Brian [24] mentions that “…there is a lack of

approaches to systematically analyze the

scope and size of the various types of SOA

projects….”

Major Success Factor in Software ProjectsSeveral authors have identified scope as a

major factor impacting project success [18],

[19], [20], [21], [22], [23].

Not found in Literature ReviewTracing the evolution of themes in project

management research, through a systematic

review of literature from 1961 to 2015, the

research identifies that despite the EVM

improvements and new approaches, scope

constraint has not been explicitly addressed,

Padalkar et al. [20]Positioning of scope management within PMBOK knowledge areas [38]

1960’s

2017

10

What is Software SCOPE acording to PMBoK?

Software project scope elements from user requirements (UR) - Adapted from Buglione [53]

Product-Scope

The PMBOK [28] defines the Product Scope as “the features and functions that characterize a product, service, or results”

Project-Scope

The PMBOK [28] defines the Project Scope is defined as “the work that needs to be accomplished to deliver a product, service, or result with the specified features and functions”.

11

What is used as Software SCOPE?

Software project scope elements from user requirements (UR) - Adapted from Buglione [53]

B. There are several approaches to measure NFR, but there is currently no consensus and of course, no standard.

A. There are ISO standards for the measurement of the size of the functional requirements, like ISO/IEC 19761 COSMIC.

C. The scope is stated only through the elements identified from the project management perspective, sometimes, included in the Work Breakdown Structure (WBS) like deliverables, easy to identify and counted frequently because the spread of specific practices, for instance Use Cases

ESM: A technique based on a standard method for measuring the functional size of software project requirements (product scope) that aims to improve monitoring the scope constraint, which in software is recognized as a key success factor. 12

Earned Scope Management (ESM)

13

What Information we can get from the ESM Originally Defined

[59] F. Valdés-Souto, Earned Scope Management�: A Case of Study of Scope Performance using COSMIC ( ISO 19761 ) with a Real Project, in: 2016 Jt. Conf. Int. Work. Softw. Meas. Int. Conf. Softw. Process Prod. Meas., Conference Piblishing Services (CPS), 2016: 

[60] F. Valdes-Souto, Earned scope management: A case of study of scope performance using Use Cases as Scope in a real project, Proc. - 27th Int. Work. Softw. Meas. IWSM 2017 12th Int. Conf. Softw. Process Prod. Meas. Mensura 2017. 

14

Current Research in ESM

WBS -UC

15

WBS – Use Case oriented

Return

Functional Size of the Software

16

ESM Aplication

Scope and features:

• 25 Use Cases (UC), 8 UC considered originally (Phase 1 or P1). 

• Phase 2 (P2) was defined with 17 additional UC.

• Life cycle: Analysis & Design, Construction and Testing, the transition was not included in the case study and the requirements elicitation was embedded in the Analysis step

Human Resources:

• In P1, 9 persons participating in the project

• In P2, 12 persons participating in the project

Functional Size:

• The P1 scope was 219 CFP distributed in 8 UC (UC 1 – UC 8)

• The P2 was 548 CFP considering 17 UC (UC 9 – UC 25)

• 767 CFP, 97 Functional Process were identified from The 25 UC.

Product Scope (using CFP)

Project Scope (using UC)

17

Productivity in Software Projects

PersonNumber of PERSONS-PERIOD

e s t ima ted to de ve l op t h e

software. Unit [PERSON-PERIOD]

EffortNumber of PERSON-HOUR

e s t ima ted to de ve l op t h e

software. Unit [PERSON-HOUR]

CostNumber of $ es t imated to

develop the software. Unit [$]

Time (Duration)Number of PERIODS estimated

to develop the software. Unit

[DAY,WEEK,MONTH,YEAR]

Resources to develop the software:

ResourceProductivity

PDREffort [CFP/PERSON-HOUR] [PERSON-HOUR/CFP]

Cost [CFP/$] [$/CFP]

Person [CFP/PERSON-PERIOD] [PERSON-PERIOD/CFP]

Duration [CFP/DAY,WEEK,MONTH,YEAR…]

[DAY,WEEK,MONTH,YEAR…/ CFP]

Software Application:

Scope Product Scope.

Unit [CFP]

Project Scope.

Unit [Deliverables / ITEMS]

Productivity / Performance

Note: Yo have a Total Budget for all the Project, is finite, will be spend each period as planned

ResourceProductivity

PDREffort [ITEMS/PERSON-HOUR] [PERSON-HOUR/ITEMS]

Cost [ITEMS/$] [$/ITEMS]

Person [ITEMS/PERSON-PERIOD] [PERSON-PERIOD/ITEMS]

Duration [ITEMS/DAY,WEEK,MONTH,YEAR…]

[DAY,WEEK,MONTH,YEAR…/ ITEMS]

18

ESM Improvements

Budget of resources (total estimated)Distinct type of resources

Distinct type of resourcesFormulas improvement

Distinct type of resourcesFormulas improvement

19

Example

20

Example

21

Conclusions

01

INCREASE OF SUCCESSFUL PROJECTS

Enabled the scope management from “product perspective” or

“project perspective”.Improves the monitor and

control for software development

projects.

02

RELEVANT INFORMATION

Provides relevant predictive

information about productivity

(performance), duration and

resources that can be used to

manage the entire software

development process; the

information could be generated

in terms of the main resources

related to software project.

03

CAPACITY OF SOFTWARE

PRODUCTION

Could be used to balance and

manage the capacity of software

production in a “software factory”

or “Internal areas”.

04

COMPLEMENT CURRENT PRACTICES

Complementary to EVM and

derivative techniques,

contributing to a more

comprehensive view of project

performance and taking the

triple constraint into account;

Complementary to Agil

techniques.

The key features of the proposed ESM technique are as follows:

Thank You

Dr. Francisco Valdés-Souto Associate ProfessorDepartment of Mathematics,Science Faculty,National Autonomous University of Mexico (UNAM)fvaldes@Ciencias.unam.mx

CHAIRMAN COSMIC Practices Committee

Mexican Software Metrics Association (AMMS)Founder AMMS