Eduardo Alves de Oliveira (MSc, CFPS, CSP)

eduaopec@yahoo.com.br

SERPRO – Brazil Federal Data Processing Service

IME – Military Institute of Engineering

Rio de Janeiro - Brazil

11/12/2015

2

• Founded in 1964;

• Public Company from

Ministry of Finance (Brazil);

• IT Public Service Provider,

Data Center, Software

Developer and Network

Backbone;

• One of the largest IT Public

Company in the World;

• Customers from Brazilian

Federal Government.

• Founded in 1792;

• Military Public University;

• The oldest Engineering

University in Brazil.

3

• Contracts using FPA;

• Contract using Agile;

• Problems in Agile Contracts;

• Solutions.

The Brazilian Government until 2009 payed the Software

Projects per hour. Since 2010 Brazilian Government

payed using FP;

These contracts had problems using only IFPUG CPM

then the Brazilian Government created a CPM extension

to measure effort (called SISP Manual);

Effort Size ($) x Functional Size (FP).

4

5

Until last year the SERPRO received Agile Projects

using Waterfall or Iterative Contracts. So the projects

had fixed scope and the rework was payed;

From the beginning of the year, Agile Projects

became an SERPRO policy and the projects must

have scope creep and rework it´s not pay. Agile

Projects have Agile Contracts.

6

1. Scope Creep x Rework;

2. Elementary Process (EP) x Sprint;

3. Poor Documentation.

7

1. Scope Creep x Rework:

- The customer change the scope but it´s doesn´t pay (per

release);

- Agile Factor: a commercial solution to the problem.

The Agile Contracts define a constant factor per

aplication that adjust the number of the final FP project.

This factor is set by a busines negotiation and not by a

statistical research on the history basis of projects. All

projects must use with or without rework.

8

2. Elementary Process (EP) x Sprint:

- EP divided into 2 or more Sprints;

- Sprint Size = Estimated Release Size / # Sprints;

- For each Sprint is paid the Sprint Size. But in the

final of release, a detailed count is made and the

difference paid.

9

3. Poor Documentation:

Problems:

- How to evidence the user requirement?

- The final count must be detailed, because

all counts are audited;

- To make traceability between the final count

and user requirement.

10

3. Poor Documentation (what is the solution of this

problem?):

( ) The counter create the documentation;

( ) Back to the hard documentation;

( ) Early Function Points (EFP);

( ) Other.

11

Agile Contracts are recent in the Brazilian Government;

Agile x FPA still have problems;

Time to count must be smaller than before;

Adopt EFP to pay projects?

Automated Function Point using EFP?

12