ACM Home Page
Please provide us with feedback. Feedback
When the project absolutely must get done: marrying the organization chart with the precedence diagram
Full text PdfPdf (314 KB)
Source International Conference on Software Engineering archive
Proceedings of the 22nd international conference on Software engineering table of contents
Limerick, Ireland
Pages: 588 - 596  
Year of Publication: 2000
ISBN:1-58113-206-9
Author
Stan Rifkin  Master Systems Inc., PO Box 8208, McLean, Virginia
Sponsors
IEEE-CS : Computer Society
SIGSOFT: ACM Special Interest Group on Software Engineering
Irish Comp Soc : Irish Computer Society
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 36,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/337180.337475
What is a DOI?

ABSTRACT

Very little is new in project planning, but this is! We present a technique to marry the organization chart with a project's task precedence diagram. This permits us to simulate the project at a micro, project-specific level never before achieved. We can perform “what-if” scenarios related to organization structures, the deployment of specific individuals and skills, and the structure of information flow and exception-handling in a project. The tool used, ViteProject, was developed over the last ten years in a Stanford University laboratory, where substantial results have been achieved when applied to design activities other than software. We present our real-world experience with several software projects, where it has improved project visibility and allowed us to rationally optimize projects in a way hitherto impossible.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Burton, Richard M., & Obel, B~rge. (1998). Strategic organizational diagnosis and design: developing
 
2
 
3
Computational & Mathematical Organization Theory. Norwell, MA: Kluwer. {Four issues per year, begun in October, 1995, ISSN 1381-298X}
 
4
Galbraith, Jay. (1974). Organization design: an information processing view. Interfaces, 4(3), 28-36.
 
5
Gersick, Connie. (1988). Time and transition in work teams: toward a new model of group development. Academy of Management Journal, 31(1), 9-41.
 
6
Jin, Yan, & Levitt, Raymond. (Fall, 1996). The virtual design team: a computational model of project organizations. Computational & Mathematical Organization Theory, 2(3), 171-196.
 
7
Levitt, Raymond. (1998). The ViteProject handbook: a user's guide to modeling and analyzing project work processes and organizations. Palo Alto: Vit~.
 
8