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.
Big Data in software engineering estimation, can be a valuable tool to improve the accuracy, efficiency, and transparency of the estimation process. However, it is important to be aware of the challenges associated with using big data before adopting this approach.
Estimating the cost and schedule of custom software development from preliminary requirements or a Concept of Operations (ConOps) document can be challenging. Software size and productivity are major drivers of software development costs. This presentation outlines a streamlined six-step process to develop a data-founded and defensible cost and schedule ROM estimate from high-level requirements/ConOps documents. A sample ConOps case study will be used to demonstrate the six-step process.
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 .