CoBRA Part
CoBRA Part
CoBRA Part
______________________
Cost Estimation, Benchmarking, and
Risk Assessment
________________________________
_____
effort estimation model
Outline
2
Recap
Project Management Methodologies-PERT
CoBRA – Effort Estimation Model
practical examples,
Graphical illustrations
Guidelines from practice
Illustration of real-world CoBRA usage
Application cases from various industrial contexts
Exercise (Do yourself)
Summery of the lecture
What next……..
Motivational Quotation for eLearning
3
The CoBRA method is a way of integrating the “Art” and the “Science” of software
estimation, which is usually believed to be a “Black Art.” The CoBRA method demystifies
the Black Art of software estimation.
–Yasushi Ishigai
Research Director at Research Center for Information Technology
Mitsubishi Research Institute, Inc., Japan
We had not been able to imagine building our own software estimation models until we
encountered the CoBRA method. As far as combining project data and expert judgment for
the purpose of software effort estimation is concerned, we can definitely say that there are
no other methods that are comparable to CoBRA.
–Morihiko Shinoda, Deputy Department Manager
–Yutaka Masaoka, Senior Engineer
Government, Public Sector Systems Division
Hitachi Solutions, Ltd, Japan
What iconic figures say about CoBRA…
5
We used the CoBRA method for early-stage estimation of system integration projects. We
were very satisfied with CoBRA because we could easily model relevant cost drivers that
are specific to our own context as well as base development productivity. From limited use
in one group, we have now expanded its use to department-wide activities.
–Yasushi Aizaki
Manager at Systems Development Division
NTT Data Sekisui Systems, Japan
I am convinced that the CoBRA method has a high potential of resolving “acquisition
issues” related to the accountability of software costs in IT business, which enduringly
persist on the side of IT customers. That’s because the models are very simple and easy to
build and can be understood even by non-IT professionals.
–Hiroshi Iwakiri
General Manager
Information Systems Business Unit
Mitsubishi Electric Corporatio
What is CoBRA?? effort estimation model
6
cost
“the amount or equivalent paid or charged for something” - cost is
defined in a monetary sense, fixed infrastructure and administrative
costs
effort
“the total work done to achieve a particular end.” - manpower spent
on performing activities aimed at providing a certain product or service
In software engineering literature and practice, “cost” is often used as a
synonym for “effort.”
Terminologies we must know before start…
8
Adam Trendowicz
Some vital question to be asked??
9
The complex and multi-dependent character of software development makes managing software
projects a challenging task.
an organization’s survival and growth require effective means for managing software projects.
effective management.
Effective project management requires considering numerous issues.
It must focus on areas that are critical for
financial success, on the
effective use of resources, on an
analysis of market potential and opportunities for innovation,
a learning environment, etc……
Effort Estimation Is the Basis for Effective Project
Management
11
Barry Boehm (1981), “Poor management can increase software costs more rapidly
than any other factor
Glass (2002) points out poor effort estimation as one of the two most common
causes of runaway projects, besides unstable requirements.
Rosencrance (2007), in her survey of more than 1,000 IT professionals, reports that
two out of the three most important causes of IT project failure are perceived to
be related to poor effort estimation
Effective project management requires reliable effort and schedule estimation.
What Is a Good Estimate?
12
13
1. expert-based
2. data-driven.
The first group bases effort predictions on the judgment of human experts,
latter group uses only measurement data to derive effort predictions.
Why the CoBRA Method?
14
accuracy of estimates.
(1) combining multiple estimation paradigms, such as expert-based and
methods
Why the CoBRA Method?
15
16
Reusable cost model: The CoBRA effort model can be reused, completely or in
parts across similar projects.
Organizational learning: The CoBRA method provides a systematic process for
eliciting knowledge hidden in the experts’ minds and in measurement data and
for documenting it within a transparent and intuitive effort model.
• Comprehensive project management support: The CoBRA method supports
a number of project management activities such as estimation, project scope
negotiations, risk analysis, benchmarking, and process improvement.
• Organizational growth: The CoBRA method provides a systematic and intuitive
approach for analyzing factors that influence the performance of software
development processes and project effort. In that sense, it supports the understanding of development
processes and helps to identify important improvement
potentials.
• Building up of a measurement system:
Principles of the CoBRA Method
17
The Cost Estimation, Benchmarking, and Risk Assessment (CoBRA method combines
multiple prediction approaches in that it aggregates techniques representing expert-
based and data-driven estimation paradigms, within one hybrid estimation method.
Nominal effort (Effort Nom) is the engineering and management effort spent on
developing a software product of a certain size in the context of a nominal project.
A nominal project is a hypothetical “ideal” project in a certain environment of an
organization (or business unit).
Principles of the CoBRA Method continues…
18
Effort overhead (EO) is the additional effort spent on overcoming imperfections of a real
project environment, such as insufficient skills of the project team. Effort overhead refers
to a nonproductive project effort spent in addition to the nominal effort.
Nominal productivity (PNom) refers to development productivity under optimal project
conditions, that is, the productivity of a nominal project where all effort factors have their
best levels. In general, productivity refers (IEEE-1045 1993) to the ratio between a
project’s output and input.
The difference between nominal and actual productivity (productivity loss) is proportional
to the portion of additional nonproductive effort
Components of an Effort Model
20