2012
DOI: 10.2298/csis110525003f
|View full text |Cite
|
Sign up to set email alerts
|

Impact of personnel factors on the recovery of delayed software projects: A system dynamics approach

Abstract: Delay in a software project may result in the loss of a market opportunity or the postponement of a dependent project. Therefore, software project managers take various steps to ensure that their project is completed on time, such as adding new members to the project team. However, adding new manpower to a delayed project may cause a negative impact on the team's productivity due to assimilation time, training overhead and communication overhead. Consequently, project managers have difficulty… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
4
0
1

Year Published

2014
2014
2024
2024

Publication Types

Select...
7

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(5 citation statements)
references
References 31 publications
0
4
0
1
Order By: Relevance
“…Abdel‐Hamid and Madnick (1987) and the constructive cost model (COCOMO) (Boehm, 1981) are the most widely known software models for PM. The COCOMO model (or COCOMO 81) was further supported by Madachy (1996) to simulate the effect of an inspection‐based software life cycle process, in line with tasks, errors and effects (Farshchi et al, 2012; Lee & Miller, 2004), technical issues (Rus et al, 1999) and risk (Lopes et al, 2015). This COCOMO model was first published in the book “Software Engineering Economics” by Boehm (1981).…”
Section: Resultsmentioning
confidence: 99%
“…Abdel‐Hamid and Madnick (1987) and the constructive cost model (COCOMO) (Boehm, 1981) are the most widely known software models for PM. The COCOMO model (or COCOMO 81) was further supported by Madachy (1996) to simulate the effect of an inspection‐based software life cycle process, in line with tasks, errors and effects (Farshchi et al, 2012; Lee & Miller, 2004), technical issues (Rus et al, 1999) and risk (Lopes et al, 2015). This COCOMO model was first published in the book “Software Engineering Economics” by Boehm (1981).…”
Section: Resultsmentioning
confidence: 99%
“…Narrative explanation [30], [33], [58], [82]- [86] Literature review [31], [87]- [89] Literature review, interview [32], [35], [ Exploring which variables to incorporate into the model and how they are causally related to others is a task that should be linked to identifying instruments to measure them. Doing this allows, in the model's practical application, the collection of data to be consistent with the purpose of the analysis.…”
Section: Methods Referencesmentioning
confidence: 99%
“…The difference between these two methods is that the former is chosen when a related and validated model is available but the actual process data are hard to access, 53 while the latter is used to check whether the model's outputs and the actual data are similar when actual (empirical) data are available. 60 Both comparison with actual data and experimental case need empirical process data to verify a model. However, the purposes of them in modeling practice are different.…”
Section: Rq2: What Methods Are Used In Vandv Of Spsms?mentioning
confidence: 99%
“…For example, comparison with other model and comparison with actual data can both be used to check the model's outputs. The difference between these two methods is that the former is chosen when a related and validated model is available but the actual process data are hard to access, 53 while the latter is used to check whether the model's outputs and the actual data are similar when actual (empirical) data are available 60 …”
Section: Findings and Mappingmentioning
confidence: 99%