A Discrete, Deterministic Model for Understanding Software Project Development Contingency Profiles

This paper describes a simple, discrete deterministic model for the allocation of project contingency as a function of project phase. When a project starts, there is always some uncertainty regarding the resources it will require. As the project proceeds, the participants discover this uncertainty a...

Full description

Bibliographic Details
Main Authors: Bruce R. Barkstrom, Paula L. Sidell
Format: Article
Language:English
Published: International Institute of Informatics and Cybernetics 2010-12-01
Series:Journal of Systemics, Cybernetics and Informatics
Subjects:
Online Access:http://www.iiisci.org/Journal/CV$/sci/pdfs/MJ667MW.pdf
id doaj-a2631890014d4bceb32249ac630e419b
record_format Article
spelling doaj-a2631890014d4bceb32249ac630e419b2020-11-24T22:56:12ZengInternational Institute of Informatics and CyberneticsJournal of Systemics, Cybernetics and Informatics1690-45242010-12-01866166A Discrete, Deterministic Model for Understanding Software Project Development Contingency ProfilesBruce R. Barkstrom0Paula L. Sidell1 retired This paper describes a simple, discrete deterministic model for the allocation of project contingency as a function of project phase. When a project starts, there is always some uncertainty regarding the resources it will require. As the project proceeds, the participants discover this uncertainty and remove it through the expenditure of resources. In addition, the project may encounter unexpected changes in its environment that force the project to change. The model assumes that the project will eventually discover a (relatively small) number of contingencies, each of which requires the same workforce and duration to resolve. Because the time of appearance and resolution time for each contingency is independent of other contingencies, there may be several overlapping contingencies the project will work on at the same time. Because the model assumes that contingencies suddenly add and subtract staff, managing staff becomes much more complex than is the case with a more uniform staffing plan. In particular, if there are appreciable hiring and firing costs, a project may find it desirable to simply retain staff that can be assigned to contingencies, even though there may be periods with no contingency work.http://www.iiisci.org/Journal/CV$/sci/pdfs/MJ667MW.pdf Project ContingencyManagement Style
collection DOAJ
language English
format Article
sources DOAJ
author Bruce R. Barkstrom
Paula L. Sidell
spellingShingle Bruce R. Barkstrom
Paula L. Sidell
A Discrete, Deterministic Model for Understanding Software Project Development Contingency Profiles
Journal of Systemics, Cybernetics and Informatics
Project Contingency
Management Style
author_facet Bruce R. Barkstrom
Paula L. Sidell
author_sort Bruce R. Barkstrom
title A Discrete, Deterministic Model for Understanding Software Project Development Contingency Profiles
title_short A Discrete, Deterministic Model for Understanding Software Project Development Contingency Profiles
title_full A Discrete, Deterministic Model for Understanding Software Project Development Contingency Profiles
title_fullStr A Discrete, Deterministic Model for Understanding Software Project Development Contingency Profiles
title_full_unstemmed A Discrete, Deterministic Model for Understanding Software Project Development Contingency Profiles
title_sort discrete, deterministic model for understanding software project development contingency profiles
publisher International Institute of Informatics and Cybernetics
series Journal of Systemics, Cybernetics and Informatics
issn 1690-4524
publishDate 2010-12-01
description This paper describes a simple, discrete deterministic model for the allocation of project contingency as a function of project phase. When a project starts, there is always some uncertainty regarding the resources it will require. As the project proceeds, the participants discover this uncertainty and remove it through the expenditure of resources. In addition, the project may encounter unexpected changes in its environment that force the project to change. The model assumes that the project will eventually discover a (relatively small) number of contingencies, each of which requires the same workforce and duration to resolve. Because the time of appearance and resolution time for each contingency is independent of other contingencies, there may be several overlapping contingencies the project will work on at the same time. Because the model assumes that contingencies suddenly add and subtract staff, managing staff becomes much more complex than is the case with a more uniform staffing plan. In particular, if there are appreciable hiring and firing costs, a project may find it desirable to simply retain staff that can be assigned to contingencies, even though there may be periods with no contingency work.
topic Project Contingency
Management Style
url http://www.iiisci.org/Journal/CV$/sci/pdfs/MJ667MW.pdf
work_keys_str_mv AT brucerbarkstrom adiscretedeterministicmodelforunderstandingsoftwareprojectdevelopmentcontingencyprofiles
AT paulalsidell adiscretedeterministicmodelforunderstandingsoftwareprojectdevelopmentcontingencyprofiles
AT brucerbarkstrom discretedeterministicmodelforunderstandingsoftwareprojectdevelopmentcontingencyprofiles
AT paulalsidell discretedeterministicmodelforunderstandingsoftwareprojectdevelopmentcontingencyprofiles
_version_ 1725654259163201536