Do certain application types have better productivity rates than others? This short paper examines the productivity rates for different application types in the ISBSG Repository. It compares statistics to determine which application is a winner in terms of productivity!
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.
Many organizations employ software development experts to develop applications that are used inhouse or sold to customers. Other organizations outsource application development to specialized, external companies. In this short paper, we examine the differences in productivity and delivery speed between in-house and outsourced application development.
This short report explains why the benchmarking of application development projects and teams is an important activity. It enables comparisons between your project and projects produced by industry leaders as a basis for improvement.
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.
This short paper discusses how ISBSG data is used by leading industry experts, including certified Software Cost Estimators, to estimate the cost of software development projects. The paper discusses the difficulties and challenges inherent in software project cost estimation. It also explores how estimation has evolved in Agile contexts. A detailed example demonstrates the steps taken to make a cost estimation for a sample project.
Software development projects often fail to meet expectations, exceed budgets, and overrun schedules. Often, the cause is bad estimation practices.
Nesma and the International Cost Estimation and Analysis Association (ICEAA) developed the Cost Estimation Body of Knowledge for Software (CEBoK-S).
This presentation addresses the industry’s main issues, CEBoK-S and aims to solve these issues. ISBSG data is used to estimate software projects using functional size and relevant historic data.
We present the methods that focus solutions to the “Next Release Problem” for agile-driven developments. This includes: new algorithm proposals and novel techniques that model how the software requirements interact .
Accurate estimations are essential for the success of your project.
Determine the factors that impact your project’s productivity.
Learn about productivity, estimation and team size in Agile.
Compare your project’s estimates to the best in the software industry.
A significant proportion of your IT systems’ budget may be spent on maintenance and support.
Learn about the importance of software size, as an important factor in estimating cost.
Discover how customer satisfaction, cost-effectiveness and quality can be maintained with outsourcing.
Learn about the factors that affect the schedule and budget of your project.
Find out about the latest news and events in the world of software metrics.