메뉴 건너뛰기




Volumn , Issue , 2010, Pages 82-87

Status communication in agile software teams: A case study

Author keywords

Awareness; Build processes; Communication; Software teams; Status information

Indexed keywords

AGILE DEVELOPMENT; AGILE SOFTWARES; AWARENESS; BEST-PRACTICES; BUILD PROCESSES; IN-DEPTH INTERVIEWS; MONITORING SYSTEM; SOFTWARE PROJECT; SOFTWARE TEAMS; STATUS INFORMATION; WORK PRACTICES;

EID: 78649844481     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSEA.2010.20     Document Type: Conference Paper
Times cited : (17)

References (13)
  • 4
    • 21644487845 scopus 로고    scopus 로고
    • Group awareness in distributed software development
    • ACM
    • C. Gutwin, R. Penner, and K. Schneider, "Group awareness in distributed software development," Proc. CSCW 04, ACM, 2004, 72-81.
    • (2004) Proc. CSCW 04 , pp. 72-81
    • Gutwin, C.1    Penner, R.2    Schneider, K.3
  • 5
    • 0003376029 scopus 로고    scopus 로고
    • Blowing the whistle on troubled software projects
    • M. Keil and D. Robey. "Blowing the whistle on troubled software projects," Com. ACM, 44 (4), 2001, pp. 87-93.
    • (2001) Com. ACM , vol.44 , Issue.4 , pp. 87-93
    • Keil, M.1    Robey, D.2
  • 7
    • 78649853376 scopus 로고    scopus 로고
    • Continuous monitoring tutorial at agile 2008
    • retrieved March 3, 2009
    • O. Rogers. "Continuous monitoring tutorial at Agile 2008" Exortech.com Blog, 2008, retrieved March 3, 2009.
    • (2008) Exortech.com Blog
    • Rogers, O.1


* 이 정보는 Elsevier사의 SCOPUS DB에서 KISTI가 분석하여 추출한 것입니다.