20:
38:, in which the knowledge product is owned and advanced by a production site in one time zone and handed off at the end of their work day to the next production site that is several time zones west to continue that work. Ideally, the work days in these time zones overlap such that when one site ends their day, the next one starts.
268:
Identified best practices are the use of agile methods and using technologies to develop FTS activities. Agile supports daily handoffs which is a critical challenge in FTS. Management tools can be used to estimate and plan schedules, manage sprints and track progress. Additionally, technologies like
131:
There are few documented cases of companies successfully applying FTS. Some companies have claimed to successfully implement FTS but these companies did not practice the daily handoffs. However, a limited amount of successful applications of FTS that did include daily handoffs of artefacts, using a
62:
Two other cases of FTS at IBM have been documented by
Treinen and Miller-Frost. The first team was spread out across a site in the United States and a site in Australia. FTS was successful for this team. The second team was spread out across a site in the United States and a site in India. In this
41:
FTS has the potential to significantly increase the total development time per day (as viewed from the perspective of a single time zone): with two sites the development time can increase to up to 16 hours, or up to 24 hours if there are three sites, reducing the development duration by as much as
124:
FTS's largest strength, spreading the development over multiple time zones, is simultaneously its largest weakness. Its distributed workflow is more complex to implement due to cultural and technical differences as well as the differences in time making coordination and communication challenging.
159:
Deal with communication: agile methodologies emphasize communication. They specifically emphasize face-to-face communication, which can be done within one site. Since FTS aims to reduce inter-site communication, the face-to-face aspect is not a large hindrance to the overall application of agile
108:. In this configuration work is distributed to workers who are available at that time. It is focused on availability and the workers have little dependency, whereas FTS is focused on duration reductions and requires dependencies between the different sites in order to perform the daily handoffs.
480:
Kroll, J., Hashmi, S. I., Richardson, I., & Audy, J. L. (2013, August). A systematic literature review of best practices and challenges in follow-the-sun software development. In Global
Software Engineering Workshops (ICGSEW), 2013 IEEE 8th International Conference on (pp. 18-23).
176:(2013) have researched papers published between 1990 and 2012 and found 36 best practices and 17 challenges for FTS. The challenges were grouped in three categories: coordination, communication and culture. These challenges should be overcome to implement FTS successfully.
58:
had the first global software team which was specifically set up to take advantages of FTS. The team was spread out across five sites around the globe. Unfortunately, in this case FTS was unsuccessful because it was uncommon to hand off the software artifacts daily.
342:
Carmel, E., Dubinsky, Y., & Espinosa, A. (2009, January). Follow the sun software development: New perspectives, conceptual foundation, and exploratory field study. In System
Sciences, 2009. HICSS'09. 42nd Hawaii International Conference on (pp. 1-9).
111:
24-hour manufacturing. This configuration focuses on making shifts fully optimize expensive resources that could not produce more by increasing the number of employees per shift. However, this driver of reducing the resource cost is not the driver of
155:
Support daily handoffs: the continuous integration and automated integration of source code allows each site to work in their own code bases during their work day, while the integration maintains updated, testable code to be used by the next
45:
It is not commonly practiced in industry and has few documented cases where it is applied successfully. This is likely because of its uncommon requirements, leading to a lack of knowledge on how to successfully apply FTS in practice.
431:
Espinosa, J. A., & Carmel, E. (2003, May). Modeling coordination costs due to time separation in global software teams. In Global
Software Development Workshop, International Conference on Software Engineering (ICSE) (pp.
185:
Time zone differences reduce opportunities for real-time collaboration. Team members have to be flexible to achieve overlap with remote colleagues. The limited overlap and the delay in responses have a negative impact on the
97:
An important step in defining FTS is to disambiguate it from other globally distributed configurations to clearly state what FTS is not. These types of similar globally distributed configurations are not FTS:
450:
Setamanit, S. O., Wakeland, W., & Raffo, D. (2007). Using simulation to evaluate global software development task allocation strategies. Software
Process: Improvement and Practice, 12(5), 491-503.
269:
conference video, emails and telephone calls are easy to implement and allow companies to perform synchronous and asynchronous communication between teams and works well in an agile environment.
128:
The main reason why FTS is difficult to implement is because the handoffs are an essential element that is hard to get right. The largest factor causing this difficulty is poor communication.
398:
Espinosa, J. A., Cummings, J. N., Wilson, J. M., & Pearce, B. M. (2003). Team boundary issues across multiple global firms. Journal of
Management Information Systems, 19(4), 157-190.
102:
Global knowledge work is defined as geographically dispersed knowledge workers working collaboratively from multiple locations. This is not FTS because there are no handoffs.
359:
Carmel, E., Espinosa, J. A., & Dubinsky, Y. (2010). " Follow the Sun" Workflow in Global
Software Development. Journal of Management Information Systems, 27(1), 17-38.
459:
Sooraj, P., & Mohapatra, P. K. (2008). Modeling the 24-h software development process. Strategic
Outsourcing: An International Journal, 1(2), 122-141.
115:
Collocated multi shifts. In contrast to FTS this configuration chooses one location where labor is cheap and runs multiple eight-hour shifts concurrently.
377:
Treinen, J. J., & Miller-Frost, S. L. (2006). Following the sun: Case studies in global software development. IBM Systems
Journal, 45(4), 773-783.
135:
Recent studies on FTS have moved to mathematical modeling of FTS. The research is focused on the issue of speed and the issues around the handoffs.
418:
407:
Yap, M. (2005, July). Follow the sun: distributed extreme programming development. In Agile
Conference, 2005. Proceedings (pp. 218-224). IEEE.
468:
Taweel, A., & Brereton, P. (2006). Modelling software development across time zones. Information and Software Technology, 48(1), 1-11.
441:
Jalote, P., & Jain, G. (2006). Assigning tasks in a 24-h software development model. Journal of Systems and Software, 79(7), 904-911.
189:
Daily handoff cycles or handing off work-in-progress are a requirement of FTS because without it the time to market cannot be decreased.
539:
577:
163:
Elicit cooperation and collaboration: as FTS requires more collaboration and cooperation, this emphasis is especially useful.
23:
World map showing part of it in the day and part at night; follow-the-sun workflow allows for continuous software work.
281:, which is scheduling work to be performed specifically during local night-time hours for reasons such as saving on
258:
144:
562:
31:
88:
Handoffs are conducted daily at the end of each shift. The next production site is several time zones west.
316:
389:
Carmel, E. (1999). Global software teams: collaborating across borders and time zones. Prentice Hall PTR.
492:
151:(2009) argue that agile software development methodologies assist the FTS principles because they:
63:
case FTS was unsuccessful because of miscommunication, time zone issues and cultural differences.
523:
507:
257:
It is of great importance to select and adapt a methodology for the daily handoffs e.g. using
147:
methodologies that are found to work well in GDSE work well with FTS. In particular, Carmel
419:"Rational Users Conference 2003. Reducing Time-To-Market Using Follow-the-Sun Techniques"
262:
19:
311:
76:
35:
571:
105:
286:
282:
508:"Sunshine 24/7: As EDS' work stops in one time zone, it picks up in another"
85:
There is always one and only one site that owns and works on the project.
34:, is a type of global knowledge workflow designed in order to reduce the
18:
524:"Following the sun: case studies in global software development"
75:
The main objective is the reduction of development duration /
55:
220:
Loss of communication richness / face-to-face communication
54:
Follow-the-sun can be traced back to the mid-1990s where
540:"Global call centre network slashes costs at Barclays"
476:
474:
132:
distributed-concurrent model, were found by Cameron.
355:
353:
351:
349:
338:
336:
334:
332:
32:globally distributed software engineering (GDSE)
373:
371:
369:
367:
365:
8:
385:
383:
82:Production sites are many time zones apart.
563:Example of use in industry - IT Support
143:As FTS is a sub-field of GDSE, the same
16:Type of workflow in software engineering
328:
235:Manage religious or national holidays.
223:Social cultural diversity difficulties
526:. IBM Systems Journal. 1 October 2006
7:
493:"Follow the moon, and save millions"
542:. Computer Weekly. 11 October 2001
506:Godinez, Victor (2 January 2007).
14:
417:Alexander Cameron (August 2003).
71:FTS is based on four principles:
248:Different technical backgrounds
491:Jeff Caruso (19 August 2009).
287:cheaper night-time electricity
1:
301:round-the-clock-development
289:or spare processing power.
594:
259:agile software development
160:development methodologies.
145:agile software development
510:. The Dallas Morning News
226:Synchronous communication
207:Managerial difficulties
192:Geographical dispersion
578:Industrial engineering
317:Change-of-shift report
232:Technical difficulties
204:Coordination breakdown
30:(FTS), a sub-field of
24:
277:A related concept is
93:Common misconceptions
22:
323:Notes and references
245:Cultural differences
298:24-hour development
229:Language difference
210:Technical platforms
25:
585:
551:
549:
547:
535:
533:
531:
519:
517:
515:
497:
496:
488:
482:
478:
469:
466:
460:
457:
451:
448:
442:
439:
433:
429:
423:
422:
414:
408:
405:
399:
396:
390:
387:
378:
375:
360:
357:
344:
340:
198:Loss of teamness
593:
592:
588:
587:
586:
584:
583:
582:
568:
567:
559:
554:
545:
543:
538:
529:
527:
522:
513:
511:
505:
501:
500:
490:
489:
485:
479:
472:
467:
463:
458:
454:
449:
445:
440:
436:
430:
426:
416:
415:
411:
406:
402:
397:
393:
388:
381:
376:
363:
358:
347:
341:
330:
325:
308:
295:
285:costs by using
279:follow-the-moon
275:
273:Follow-the-moon
263:waterfall model
255:
242:
217:
201:Number of sites
195:Cost estimation
182:
170:
141:
122:
95:
69:
52:
17:
12:
11:
5:
591:
589:
581:
580:
570:
569:
566:
565:
558:
557:External links
555:
553:
552:
536:
520:
502:
499:
498:
483:
470:
461:
452:
443:
434:
424:
409:
400:
391:
379:
361:
345:
327:
326:
324:
321:
320:
319:
314:
312:Time to market
307:
304:
303:
302:
299:
294:
291:
274:
271:
254:
253:Best practices
251:
250:
249:
246:
241:
238:
237:
236:
233:
230:
227:
224:
221:
216:
213:
212:
211:
208:
205:
202:
199:
196:
193:
190:
187:
181:
178:
169:
166:
165:
164:
161:
157:
140:
137:
121:
118:
117:
116:
113:
109:
103:
94:
91:
90:
89:
86:
83:
80:
77:time to market
68:
65:
51:
48:
36:time to market
28:Follow-the-sun
15:
13:
10:
9:
6:
4:
3:
2:
590:
579:
576:
575:
573:
564:
561:
560:
556:
541:
537:
525:
521:
509:
504:
503:
494:
487:
484:
477:
475:
471:
465:
462:
456:
453:
447:
444:
438:
435:
428:
425:
420:
413:
410:
404:
401:
395:
392:
386:
384:
380:
374:
372:
370:
368:
366:
362:
356:
354:
352:
350:
346:
339:
337:
335:
333:
329:
322:
318:
315:
313:
310:
309:
305:
300:
297:
296:
292:
290:
288:
284:
280:
272:
270:
266:
264:
260:
252:
247:
244:
243:
239:
234:
231:
228:
225:
222:
219:
218:
215:Communication
214:
209:
206:
203:
200:
197:
194:
191:
188:
186:coordination.
184:
183:
179:
177:
175:
167:
162:
158:
154:
153:
152:
150:
146:
138:
136:
133:
129:
126:
119:
114:
110:
107:
104:
101:
100:
99:
92:
87:
84:
81:
78:
74:
73:
72:
66:
64:
60:
57:
49:
47:
43:
39:
37:
33:
29:
21:
544:. Retrieved
528:. Retrieved
512:. Retrieved
486:
464:
455:
446:
437:
427:
412:
403:
394:
278:
276:
267:
256:
180:Coordination
173:
171:
148:
142:
134:
130:
127:
123:
120:Difficulties
106:24/7 service
96:
70:
61:
53:
44:
40:
27:
26:
293:Other terms
546:31 October
530:31 October
514:31 October
283:datacenter
168:Challenges
67:Principles
572:Category
306:See also
432:64-68).
261:or the
240:Culture
139:Methods
50:History
174:et al.
172:Kroll
149:et al.
481:IEEE.
343:IEEE.
156:site.
42:67%.
548:2008
532:2008
516:2008
112:FTS.
265:.
56:IBM
574::
473:^
382:^
364:^
348:^
331:^
550:.
534:.
518:.
495:.
421:.
79:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
