\documentclass[10pt]{article}

\usepackage{fullpage}
\usepackage{setspace}
\usepackage{parskip}
\usepackage{titlesec}
\usepackage[section]{placeins}
\usepackage{xcolor}
\usepackage{breakcites}
\usepackage{lineno}
\usepackage{hyphenat}





\PassOptionsToPackage{hyphens}{url}
\usepackage[colorlinks = true,
            linkcolor = blue,
            urlcolor  = blue,
            citecolor = blue,
            anchorcolor = blue]{hyperref}
\usepackage{etoolbox}
\makeatletter
\patchcmd\@combinedblfloats{\box\@outputbox}{\unvbox\@outputbox}{}{%
  \errmessage{\noexpand\@combinedblfloats could not be patched}%
}%
\makeatother


\usepackage{natbib}




\renewenvironment{abstract}
  {{\bfseries\noindent{\abstractname}\par\nobreak}\footnotesize}
  {\bigskip}

\titlespacing{\section}{0pt}{*3}{*1}
\titlespacing{\subsection}{0pt}{*2}{*0.5}
\titlespacing{\subsubsection}{0pt}{*1.5}{0pt}


\usepackage{authblk}


\usepackage{graphicx}
\usepackage[space]{grffile}
\usepackage{latexsym}
\usepackage{textcomp}
\usepackage{longtable}
\usepackage{tabulary}
\usepackage{booktabs,array,multirow}
\usepackage{amsfonts,amsmath,amssymb}
\providecommand\citet{\cite}
\providecommand\citep{\cite}
\providecommand\citealt{\cite}
% You can conditionalize code for latexml or normal latex using this.
\newif\iflatexml\latexmlfalse
\providecommand{\tightlist}{\setlength{\itemsep}{0pt}\setlength{\parskip}{0pt}}%

\AtBeginDocument{\DeclareGraphicsExtensions{.pdf,.PDF,.eps,.EPS,.png,.PNG,.tif,.TIF,.jpg,.JPG,.jpeg,.JPEG}}

\usepackage[utf8]{inputenc}
\usepackage[T2A]{fontenc}
\usepackage[ngerman,polish,english]{babel}



\usepackage{float}








\begin{document}

\title{Impact of individual competence on agile effort estimation in academic
setting}



\author[1]{Luka Fürst}%
\author[1]{Tomaž Hovelja}%
\author[1]{Marko Poženel}%
\author[1]{Damjan Vavpotič}%
\affil[1]{Univerza v Ljubljani Fakulteta za Racunalnistvo in Informatiko}%


\vspace{-1em}



  
  \date{May 16, 2024}


\begingroup
\let\center\flushleft
\let\endcenter\endflushleft
\maketitle
\endgroup





\selectlanguage{english}
\begin{abstract}
Effort estimation is an important activity in agile software
development. The goal of the presented study was to determine the
influence of individual competence on software development effort
estimation. In particular, we measured both the accuracy of effort
estimation and the duration of the estimation process itself, both for
three different estimation methods. The subjects of our study were teams
of students of a graduate-level software engineering course at the
University of Ljubljana, Faculty of Computer and Information Science.
Based on the grades that individual students attained in their
undergraduate study, we classified each team as `high-competence' or
`low-competence' and additionally as `heterogeneous' or `homogeneous'
(the criterion here being the variance of the members' average grades).
We found out that there was no significant difference in effort
estimation accuracy neither between high-competence and low-competence
teams nor between heterogeneous and homogeneous teams, regardless of
which estimation method was used. However, high-competence teams spent
significantly less time on effort estimation than low-competence ones.
Likewise, for two of the employed estimation methods, heterogeneous
teams completed effort estimation in a significantly shorter time than
homogeneous teams. These results might benefit both academic and
professional community.%
\end{abstract}%



\sloppy




\selectlanguage{english}
\FloatBarrier
\end{document}

