ExpoQA16 Ignacio Ton Ledamc
ExpoQA16 Ignacio Ton Ledamc
Ton Dekkers
Ignacio Lopez Carrillo
1
Why NESMA
About LEDAmc
The cuestion
Want to improve
Typical Problems
What to do
Examples
And in Agile
2
About Nesma
Ton Dekkers
Nesma|President The renewed website is
Interdependent | Software Cost Engineer organized into 6 themes:
ISBSG | Past President - Board
COSMIC | IAC member Benchmarking
Outsourcing
Partners Productivity
Galorath | US Project Control
Leda | ES Estimation
Metrieken.nl | NL Sizing methods
PRICE systems | UK
Vision
independent from customers and suppliers
nesma is the not-for-profit organisation in the area of predictability of the cost of the
delivery and the maintenance of software
nesma joins as much as possible existing standards with a different focus than measurement
nesma connects surrounding attention domains
nesma is independent from customers and suppliers
3
Nesma Miniguides Software metrics in contracts
http://nesma.org/publications/downloads/guides/software-metrics-in-contracts/
4
About LEDAmc
Spanish company
> 100 employees
Office in Madrid and Bogota
Customers in Europe, USA, LATAM and ASIA
Quantify Focussed in Outsourcing Management
Optimize > 70% FP certified consultants in Spain
ROI service commitment (47M 2015)
Projections
5
Risk SW Gobernance
Content Management
Size
Persons
Technology Process Factors Risk SW Consecuences Economical
Time
Technology Gobernance
Management Imagen Performance
Experience Productivity Quality
Model
Projects
Score Card Testing
Test Gobernance Predictions
Decision Making Optimize Project Risk Sizing Team
Office
6
The question
7
The question
Esfuerzo de pruebas:
Disminucin del coste por reduccin de tarifa
8
Test Teams / Test Factories
Lack of this
Testware metrics
Some goes directly
enhance
?
capability
to this model
Lack of reference
values
Testing
factories Lack of results expected
enhance
?
effectiveness
RFP Testing Factory
Functional Testing
Miniguide
9
Typical Problems
Dont worry
Test Management
Different Test and Defect tracking Be busy
environment common tools
management
Different
Highly detailed Location
documentation
Organizational
Non Not enough
professional information in
profiles Quality Gates
Capability
?
High level Human Decision
of rotation resources making
Performance
No information
Effectiveness Subjetive in earlier stage
Payment Model
Savings (MH, TC)
Economical
Project
Planning delay
Over sizing
of testing
resources Duplication of Not objective
cost for getting testing estimation
good quality model Not control
Not measurable of outsourced
target of service
testing results
10
What to do to mitigate problems?
Four Stages during the testing outsourcing process to mitigate the problems :
11
Activities
RFP preparation
RFP adjudication
13
Activities
Service Operation
Audit the level of Enhancement of the Related with Quality defects in the next
Control testing testing phases
details of the test case testing activities in the Gate and compared
productivity
designed testing levels with initial estimation
14
Activities
Perform continuous
Perform ROI report of Define target of
improvement model
the testing service enhacement
(TMMi)
Perform bonus/penalty
scheme
15
Examples RFP Preparation: Test-ware estimation
Estimaciones de Testware
16
Examples RFP Preparation: Sizing of testing resources
Estimaciones de Testware
17
Examples RFP Preparation: Testing Productivity figures
Caso de xito
18
Saving money Using the Mini Guide
Caso de xito
TC
28.275
17.400
Control
No control
0
1 year 1,6 years Time
19
Software Testing metrics in Agile projects
Estimaciones de Testware
History Dont
Factories Point with compare
different persons
criteria and teams
Average test cases designed by person [/ day] / 1 designedTest Case Agile teams
Average test cases executed by person [/ day] / 1 executed Test case Releases
Average defects checked by person [/ day] / 1 detected defect Sprints
# detected defects by History Point / 1 avoided defect
% total errors detected QA / UATs / Production / 1 tested History Point
20
Software Testing metrics in Agile pojects
Estimaciones de Testware
Be agile,
flexible, but
not fragile
21
Estimaciones de Testware
22