Control all phases of the projects
This short paper summarises the results of the recently published Global Trend Research Report on Software Engineering, published by the Information-technology Promotion Agency (IPA) of Japan. Many experts from the software measurement community, (e.g., from Nesma, COSMIC, IFPUG, ISBSG, etc.,) were interviewed and provided input for this research.
In this short paper, the difference in productivity (i.e., effort distribution) between traditional and agile projects is analysed. It explores the importance of optimal effort distributions in agile development and discusses general trends. It compares a subset of ISBSG project data to general effort distribution observed in agile development teams.
This short paper describes and compares two methods of measurement used in software projects – Story Points and Functional Size Measurement. The choice of metrics can significantly influence decision-making and behavior within an organization. Therefore Story Points and Functional Size Measurement are rated for their relevance to “good” metrics (e.g., cost effectiveness).
We will look at the XL projects in the ISBSG database. These are projects with a functional size that is greater than 3000 Nesma or IFPUG function Points. The following characteristics will be investigated: delivery rate and speed, projects per industry sector, project duration based on programming language, year of completion.
ITIL4 has 7 recommendations to improving services. They are relevant for all businesses. Use real-life examples to apply these principles from a measurement perspective .
This short paper determines whether there are key factors that influence the productivity and delivery speed of CRM projects.
This short paper examines a high-level business case to to rebuild a Cobol legacy application in Java. ISBSG Data, for similar Java projects, provides metrics for: cost, effort, maintenance and support. This information is used as the basis for the business case.
In this short paper, we explain the way ISBSG data can be used to contract application development teams based on output instead of the usual Time & Materials method.
With agile, you choose to develop the functionality that provides the most value for the customer, post-development. What functionality does the customer receive and how can it be measured?
Learn how ISBSG data is used in practice to make better decisions regarding Application Development related issues.
