DEPENDENCY FORECASTING IN THE DISTRIBUTED AGILE ORGANIZATION.
The article focuses on task coordination in globally distributed system development (GDSD). The authors argue that agile project management of GDSD is challenging. Constant communications is a necessity especially in projects that have a long duration or involve many software developers. The auth...
| Publicado en: | Communications of the ACM Vol. 49; no. 10; pp. 55 - 57 |
|---|---|
| Autores principales: | , |
| Formato: | Artículo |
| Publicado: |
Association for Computing Machinery
Oct2006
|
| Materias: | |
| Acceso en línea: | Ver este registro en EBSCOhost |
| fields | @attributes: recordID: 1 pdfLink: plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=22665305&site=ehost-live header: @attributes: shortDbName: hlh uiTerm: 22665305 longDbName: Humanities International Complete uiTag: AN controlInfo: bkinfo: jinfo: jid: 00010782 ACM jtl: Communications of the ACM issn: 00010782 maglogo: N pubinfo: dt: Oct2006 vid: 49 iid: 10 pid: 68 pub: Association for Computing Machinery artinfo: ui: 22665305 10.1145/1164394.1164420 ppf: 55 ppct: 2 formats: tig: atl: DEPENDENCY FORECASTING IN THE DISTRIBUTED AGILE ORGANIZATION. aug: au: WAGSTROM, PATRICK HERBSLEB, JAMES affil: Ph.D. candidate, Computation, Organizations, and Society Program, Department of Engineering and Public Policy, Carnegie Mellon University, Pittsburgh, PA. Nico A. Haberman Associate Professor of Computer Science, Carnegie Mellon University, Pittsburgh, PA Director of the Software Industry Center, Carnegie Mellon University, Pittsburgh, PA su: Computer software development Project management Management Business communication Cooperation International business enterprises sug: subj: Computer software development Project management Management Business communication Cooperation International business enterprises ab: The article focuses on task coordination in globally distributed system development (GDSD). The authors argue that agile project management of GDSD is challenging. Constant communications is a necessity especially in projects that have a long duration or involve many software developers. The authors describe an automated method in order to determine who should be included in communications on specific aspects of a project. Instead of relying on project management staff to constantly redraw communications "maps," the authors propose an automated process that examines who is working on specific areas of the software's code. pubtype: Periodical doctype: Article src: R language: English refInfo: copyright: @attributes: flag: Y dt: @attributes: year: 2006 holdings: @attributes: islocal: N |
|---|