Extreme programming explained: embrace change
Extreme programming explained: embrace change
An empirical study of global software development: distance and speed
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
The Mythical Man-Month: Essays on Softw
The Mythical Man-Month: Essays on Softw
Test Driven Development: By Example
Test Driven Development: By Example
Computer
Surviving Global Software Development
IEEE Software
A Design-based Model for the Reduction of Software Cycle Time
HICSS '96 Proceedings of the 29th Hawaii International Conference on System Sciences Volume 1: Software Technology and Architecture
Assigning tasks in a 24-h software development model
Journal of Systems and Software - Special issue: Selected papers from the 11th Asia Pacific software engineering conference (APSEC 2004)
Following the sun: case studies in global software development
IBM Systems Journal
The Social Dynamics of Pair Programming
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Evaluating Pair Programming with Respect to System Complexity and Programmer Expertise
IEEE Transactions on Software Engineering
The Effect of Pairs in Program Design Tasks
IEEE Transactions on Software Engineering
How Pair Programming Really Works
IEEE Software
Distributed agile: project management in a global environment
Empirical Software Engineering
XP expanded: distributed extreme programming
XP'05 Proceedings of the 6th international conference on Extreme Programming and Agile Processes in Software Engineering
Timeboxing: a process model for iterative software development
Journal of Systems and Software
Hi-index | 0.00 |
With globalization, many software corporations have engineering groups working in different time zones. While a globally distributed team with engineers in different time-zones has been leveraged successfully in maintenance for reducing response time, not much work has been done on reducing the time in a development project, and globally distributed teams are mostly used to provide capacity benefit. We propose the use of global-pairs as a simple method of organizing global resources for leveraging time zone differences for reducing the cycle time. Instead of assigning tasks to individual resources, a project can assign tasks to global-pairs, each having one resource working in one time zone and the other in opposite time zone. Each global-pair is self-organizing and divides the work in a manner such that work within a task progresses continuously, thereby reducing the time to complete the assigned task by up to a half. Use of global pairs does not unduly complicate project management -- a key difficulty in global software development -- as a project looks same as before, except that some of the resources now "work faster". Initial experiment with a global pair in the coding phase of a live project suggests that the concept is feasible and can reduce the cycle time significantly.