To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
The technical storage or access that is used exclusively for statistical purposes.
The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
Benchmarking
/in benchmarkingUsing the example of Toyota, we will learn the main practices that allow maximum digital transformation: benchmarking.
Historical Data
/in project controlIn DevOps the “Third Way” means “continuous experimentation & learning”. This is the highest maturity level for decision-making.
Agile Team
/in agileManaging the IT function in management and development is more important than ever. It is wrongly assumed that agile, DevOps or multidisciplinary teams do not need planning or leadership.
Discover What ISBSG Offers
/in recommendedFind out what ISBSG offers and how ISBSG can help you and your project, with this informative guide.
Use of Function Points
/in sizingFunctional size (function points) is universally considered to be the square meter of the software
industry. It is the only international standard used to measure the size of software in a standardized,
objective, repeatable, verifiable and defensible way.
Cost Estimation
/in estimationA trading company would like to replace a large legacy application with an application that offers the same functionality.
Senior management understands that an accurate estimate is the basis for a successful project. They intend to carry out an independent cost estimation by a specialized third party.
In this case study, the steps that were carried out are listed and the results are given.
Software Productivity Versus Speed
/in productivityThe Project Delivery Rate of a project expresses how many effort hours were
spent, on average, to create one function point. Speed expresses how many
function points are created per calendar month. So there is a relationship since
both metrics refer to effort and time. The question is: “How are these metrics
related?”
Low-code Project Productivity
/in productivityA high-level analysis is given of the productivity differences between traditional languages, such as Java or .Net and low code technologies (i.e. drag and drop).
Java Project Productivity
/in productivityJava is a high-level, class-based, object-oriented programming language that is designed to have as few implementation dependencies as possible. There is a lot of available data of Java projects in the 2021 ISBSG Development & Enhancement repository – over 2000 projects. This short paper examines the productivity of these projects.
Software Productivity Measurement
/in productivity, recommendedIn this industry report, Challenges in Productivity Measurement in the software industry are
addressed and the way ISBSG data can be used to benchmark productivity of completed
projects, releases and sprints is explained.
Software Sizing Methods
/in sizingFunctional size (function points) is the only international standard to measure the size of software in a standardized, objective, repeatable, verifiable and therefore defensible way. This report examines methods used by projects in the ISBSG Data Repository.
Software Benchmarking Goals
/in benchmarkingAn objective of software benchmarking is to obtain a balanced approach to software development ensuring that important project factors are considered.
Project Estimation
/in estimationTime and time again, the software industry struggles to come up with accurate estimates for software development projects, releases, or sprints. Lack of understanding of the performance of development teams in combination with low maturity estimation processes, often result in overly optimistic project estimates that are highly probable to result in failing projects and severe cost and schedule overruns.
Agile Project Productivity
/in agileISBSG has collected more data for projects carried out in an agile-way of working. In this short paper, the difference in productivity between traditional and agile projects is analyzed.
Agile Team Size Estimation
/in agileFor agile teams, it’s usually quite easy to estimate the cost. The important management questions are: How many people should be in the team in order to have specific functionality at a given time? How can progress be measured during this time?