Managing software project teams is a complex task further
complicated by a continued increase in the size and complexity of
software-intensive systems and the distribution of project teams.
Given limited project resources, distributed teams require
appropriate team processes and adequate tool support to help them
remain focused on the most critical design tasks, thereby
structuring the design process and improving team coordination.
However, existing project management tools typically fall short.
Software project management as a discipline is not unlike humancomputer
interaction (HCI) in that both combine technical
concerns with human psychological concerns. Both could benefit
from a more systematic approach to applying theory to practice.
One proposed approach to the science of design involves
constructing a record of design rationale by leveraging design
knowledge from previous projects. Extending the reuse paradigm
from product-related knowledge to process-related knowledge
could improve software project management by helping teams to
externalize and maintain a physical record of their design process.
A risk management model could help teams to prioritize design
knowledge, allowing them to focus their effort on key design
tasks.
Description
Software project management as a discipline is not unlike humancomputer
interaction (HCI) in that both combine technical
concerns with human psychological concerns.
%0 Conference Paper
%1 1167319
%A Smith, Jamie L.
%A Bohner, Shawn A.
%A McCrickard, D. Scott
%B ACM-SE 43: Proceedings of the 43rd annual Southeast regional conference
%C New York, NY, USA
%D 2005
%I ACM
%K hci projectmanagement survey
%P 300--305
%R http://doi.acm.org/10.1145/1167253.1167319
%T Project management for the 21st century: supporting collaborative design through risk analysis
%X Managing software project teams is a complex task further
complicated by a continued increase in the size and complexity of
software-intensive systems and the distribution of project teams.
Given limited project resources, distributed teams require
appropriate team processes and adequate tool support to help them
remain focused on the most critical design tasks, thereby
structuring the design process and improving team coordination.
However, existing project management tools typically fall short.
Software project management as a discipline is not unlike humancomputer
interaction (HCI) in that both combine technical
concerns with human psychological concerns. Both could benefit
from a more systematic approach to applying theory to practice.
One proposed approach to the science of design involves
constructing a record of design rationale by leveraging design
knowledge from previous projects. Extending the reuse paradigm
from product-related knowledge to process-related knowledge
could improve software project management by helping teams to
externalize and maintain a physical record of their design process.
A risk management model could help teams to prioritize design
knowledge, allowing them to focus their effort on key design
tasks.
%@ 1-59593-059-0
@inproceedings{1167319,
abstract = {Managing software project teams is a complex task further
complicated by a continued increase in the size and complexity of
software-intensive systems and the distribution of project teams.
Given limited project resources, distributed teams require
appropriate team processes and adequate tool support to help them
remain focused on the most critical design tasks, thereby
structuring the design process and improving team coordination.
However, existing project management tools typically fall short.
Software project management as a discipline is not unlike humancomputer
interaction (HCI) in that both combine technical
concerns with human psychological concerns. Both could benefit
from a more systematic approach to applying theory to practice.
One proposed approach to the science of design involves
constructing a record of design rationale by leveraging design
knowledge from previous projects. Extending the reuse paradigm
from product-related knowledge to process-related knowledge
could improve software project management by helping teams to
externalize and maintain a physical record of their design process.
A risk management model could help teams to prioritize design
knowledge, allowing them to focus their effort on key design
tasks.},
added-at = {2008-08-01T12:14:07.000+0200},
address = {New York, NY, USA},
author = {Smith, Jamie L. and Bohner, Shawn A. and McCrickard, D. Scott},
biburl = {https://www.bibsonomy.org/bibtex/2c7879dc00e8c4d1bbe15483fab82b96a/boehr},
booktitle = {ACM-SE 43: Proceedings of the 43rd annual Southeast regional conference},
description = {Software project management as a discipline is not unlike humancomputer
interaction (HCI) in that both combine technical
concerns with human psychological concerns.},
doi = {http://doi.acm.org/10.1145/1167253.1167319},
interhash = {ba5d0b9842aba8245af0df80ef6a70a6},
intrahash = {c7879dc00e8c4d1bbe15483fab82b96a},
isbn = {1-59593-059-0},
keywords = {hci projectmanagement survey},
location = {Kennesaw, Georgia},
pages = {300--305},
publisher = {ACM},
timestamp = {2008-11-12T22:24:17.000+0100},
title = {Project management for the 21st century: supporting collaborative design through risk analysis},
year = 2005
}