Please use this identifier to cite or link to this item: http://hdl.handle.net/20.500.11889/4151
DC FieldValueLanguage
dc.contributor.authorTaweel, Adel-
dc.contributor.authorBrereton, Pearl-
dc.date.accessioned2017-01-17T10:47:49Z-
dc.date.available2017-01-17T10:47:49Z-
dc.date.issued2002-
dc.identifier.urihttp://hdl.handle.net/20.500.11889/4151-
dc.description.abstractThe empirical study described in this paper was carried out as part of a research project investigating the potential for reducing the time needed to carry out software engineering tasks (and hence to deliver software products) through the use of around the clock working. The working style being addressed is one where a task is passed in a sequential manner from one software engineer to another ‘across time zones’. We call this sequential collaborative software engineering (SCSE). A general three-site scenario is illustrated in Figure 1, and shows: • the time differences between sites (which may involve some overlap); • the reporting time when, at the end of a working period or shift, a developer records progress made; • the catching up time, when a developer catches up with the work carried out during the previous shift. As well as undertaking an empirical study of SCSE, our research has involved the development of a set of equations which models the relationships between estimated development time using SCSE, estimated• distribution effort loss, which is the time lost when a developer at one site fails to complete a task on which a subsequent developer is depending. The aims of our empirical study were to illustrate the feasibility of employing this type of work pattern and to identify the critical success factors for SCSE. We also expected to obtain some values for the associated overheads (such as reporting time and catching up time) for the particular experimental context. The remainder of the paper is organised as follows. Section 2 and 3 describe the preparatory activities (such as the selection of subjects, the design of the study and document preparation) and the execution of the selected task. Section 4 and 5 summarise analysis and observations, critical success factors, and final remarks. 2 Preparatory activitiesen_US
dc.language.isoen_USen_US
dc.subjectComputer software - Development - Managementen_US
dc.subjectVirtual work teams - Managementen_US
dc.subjectBusiness communicationen_US
dc.titleDeveloping software across time zones: an exploratory empirical studyen_US
dc.typeArticleen_US
newfileds.departmentEngineering and TechnologyEngineering and Technologyen_US
newfileds.item-access-typeopen_accessen_US
newfileds.thesis-prognoneen_US
newfileds.general-subjectnoneen_US
item.fulltextWith Fulltext-
item.grantfulltextopen-
item.languageiso639-1other-
Appears in Collections:Fulltext Publications
Files in This Item:
File Description SizeFormat
Developing_Software_Across_Time_Zones_An_Explorato.pdf366.82 kBAdobe PDFView/Open
Show simple item record

Page view(s)

142
Last Week
0
Last month
1
checked on Apr 14, 2024

Download(s)

62
checked on Apr 14, 2024

Google ScholarTM

Check


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.