Knowledge sharing and trust in collaborative requirements analysis

System Dynamics Review

Volumn 24, Issue 3, 2008, Pages 265-297

  Luna Reyes, Luis Felipe ^a   Black, Laura J ^b   Cresswell, Anthony M ^c   Pardo, Theresa A ^c  

^a UNIVERSIDAD DE LAS AMÉRICAS PUEBLA   (Mexico)

^b MONTANA STATE UNIVERSITY   (United States)

^c STATE UNIVERSITY OF NEW YORK   (United States)

Author keywords

[No Author keywords available]

Indexed keywords

EMPIRICAL ANALYSIS; INFORMATION SYSTEM; INFORMATION TECHNOLOGY; KNOWLEDGE; PROJECT ASSESSMENT;

EID: 63449087691     PISSN: 08837066     EISSN: 10991727     Source Type: Journal    
DOI: 10.1002/sdr.404     Document Type: Article

References (88)

1. Abdel-Hamid TK. 1984. The dynamics of software development project management: an integrative system dynamics perspective. PhD thesis, MIT Sloan School of Management: Cambridge, MA.
2. Abdel-Hamid TK. 1989. The dynamics of software project staffing: a system dynamics-based simulation approach. IEEE Transactions on Software Engineering 15(2): 109-119.
3. Abdel-Hamid TK, Madnick SE. 1990. The elusive silver lining: how we fail to learn from software development failures. Sloan Management Review 32: 39-48.
4. Abdel-Hamid TK, Madnick SE. 1991. Software Project Dynamics: An Integrated Approach. Prentice-Hall: Englewood Cliffs, NJ.
5. Andersen DF, Richardson GP. 1997. Scripts for group model building. System Dynamics Review 13(2): 107-129.
6. Argyris C, Schön DA. 1978. Organizational Learning: A Theory of Action Perspective. Addison-Wesley: Reading, MA.
7. Bannon L. 1995. The politics of design: representing work. Communications of the ACM 38(9): 66-68.
8. Bechky B. 2003. Sharing meaning across occupational communities: the transformation of understanding on a production floor. Organization Science 14(3): 312-330.
9. Black LJ. 2002. Collaborating across boundaries: theoretical, empirical, and simulated explorations. PhD dissertation, Sloan School of Management, MIT: Cambridge, MA.
10. Black LJ, Carlile PR, Repenning NP. 2004. A dynamic theory of expertise and occupational boundaries in new technology implementation: building on Barley's study of CT scanning. Administrative Science Quarterly 49(4): 572-607.
11. Bourdieu P. 1977. Outline of a Theory of Practice. Cambridge University Press: Cambridge, U.K.
12. Butler JK. 1999. Trust expectations, information sharing, climate of trust, and negotiation effectiveness and efficiency. Group and Organization Management 24(2): 217-238.
13. Byrd TA, Cossick KL, Zmud RW. 1992. A synthesis of research on requirements analysis and knowledge acquisition techniques. MIS Quarterly 16(1): 117-138.
14. Carlile P. 2002. A pragmatic view of knowledge and boundaries: boundary objects in new product development. Organization Science 13(4): 442-455.
15. Carlile P. 2004. Transferring, translating and transforming: an integrative framework for managing knowledge across boundaries. Organization Science 15(5): 555-568.
16. Chiles TH, McMackin JF. 1996. Integrating variable risk preferences, trust, and transaction cost economics. Academy of Management Review 21(1): 73-99.
17. Cook S, Brown J. 1999. Bridging epistemologies: the generative dance between organizational knowledge and organizational knowing. Organization Science 10(4): 381-400.
18. Cooper KG. 1980a. Strategic Analysis for Program Management: A Computer-Based Aid for the Senior Management of Large-Scale Design and Construction Programs. Pugh-Roberts Associates: Cambridge, MA.
19. Cooper KG. 1980b. Naval ship production: a claim settled and a framework built. Interfaces 10(6): 20-36.
20. Cooper KG. 1994. The $2,000 hour: how managers influence project performance through the rework cycle. Project Management Journal 25(1): 11-24.
21. Cresswell AM, Pardo TA, Thompson F, Canestraro DS, Cook M, Black LJ, Luna LF, Martinez IJ, Andersen DF, Richardson GP. 2002. Modeling intergovernmental collaboration: a system dynamics approach. In Proceedings of the Hawaiian International Conference on System Sciences 35, Hawaii.
22. Davidson E. 2002. Technology frames and framing: a socio-cognitive investigation of requirements determination. MIS Quarterly 26(4): 329-358.
23. Dawes SS, Pardo TA, Simon S, Cresswell AM, LaVigne MF, Andersen DF, Bloniarz PA. 2004. Making Smart IT Choices: Understanding Value and Risk in Government IT Investments. University at Albany: Albany, NY.
24. DeMarco T. 1982. Controlling Software Projects: Management, Measurement and Estimation. Yourdon Press: New York.
25. Dodgson M. 1993. Learning, trust, and technological collaboration. Human Relations 46(1): 77-95.
26. Dyer J, Singh H. 1998. The relational view: cooperative strategy and sources of inter-organizational competitive advantage. Academy of Management Review 23(4): 660-679.
27. Eriksson H. 1992. A survey of knowledge acquisition techniques and tools and their relationship to software engineering. Journal of Systems and Software 19: 97-107.
28. Ford DN, Sterman JD. 1998. Dynamic modelling of product development processes. System Dynamics Review 14(1): 31-68.
29. Ford DN, Anderson S, Damron A, de Las Casas R, Gokmen N, Kuennen S. 2004. Managing constructability reviews to reduce highway project durations. ASCE Journal of Construction Engineering and Management 130(1): 33-42.
30. Glaser BG, Strauss AL. 1967. The Discovery of Grounded Theory: Strategies for Qualitative Research. Aldine: Chicago, IL.
31. Graham AK. 2000. Beyond pm 101: lessons for managing large development programs. Project Management Journal 31(4): 7-18.
32. Hart P, Saunders C. 1997. Power and trust: critical factors in the adoption and use of electronic data interchange. Organization Science 8(1): 23-42.
33. Henderson K. 1991. Flexible sketches and inflexible data bases: visual communication, conscription devices, and boundary objects in design engineering. Science, Technology, and Human Values 16(4): 448-473.
34. Hildreth P, Kimble C. 2002. The duality of knowledge. Information Research 8(1): 24.
35. Jackson M. 1997. The meaning of requirements. Annals of Software Engineering 3: 5-21.
36. Jones G, George J. 1998. The experience and evolution of trust: implications for cooperation and teamwork. Academy of Management Review 23(3): 531-546.
37. Katsamakas E. 2007. Knowledge processes and learning options in networks: evidence from telecommunications. Human Systems Management 26(3): 181-192.
38. King S. 2000. Building trust among members of a work team: one facilitator's experiences. Group Facilitation 2(2): 15-21.
39. Kraut RE, Streeter LA. 1995. Coordination in software development. Communications of the ACM 38(3): 69-81.
40. Kumar N. 1996. The power of trust in manufacturer-retailer relationships. Harvard Business Review 74(6): 92-105.
41. Lave J. 1988. Cognition in Practice. Cambridge University Press: Cambridge, U.K.
42. Levin D, Cross R, Abrams L, Lesser E. 2002. Trust and Knowledge Sharing: A Critical Combination. IBM Institute for Knowledge-Based Organizations: Somers, NY.
43. Levina N. 2005. Collaborating on multiparty information systems development projects: a collective reflection-in-action view. Information Systems Research 16(2): 109-130.
44. Levina N, Vaast E. 2005. Competence in practice: Implications for implementation and use of information systems. MIS Quarterly 29(2): 335-363.
45. Luna-Reyes LF. 2004. Collaboration, trust and knowledge sharing in information-technology-intensive projects in the public sector. PhD dissertation, School of Information Science and Policy, University at Albany: Albany, NY.
46. Luna-Reyes LF, Martinez-Moyano IJ, Pardo TA, Cresswell AM, Andersen DF, Richardson GP. 2006. Anatomy of a group model-building intervention: building dynamic theory from case study research. System Dynamics Review 22(4): 291-320.
47. Lyneis JM, Ford DN. 2007. System dynamics applied to project management: a survey, assessment, and directions for future research. System Dynamics Review 23(2/3): 157-189.
48. Lyytinen K, Robey D. 1999. Learning failure in information systems development. Information Systems Journal 9(2): 85-102.
49. Majchrzak A, Cooper LP, Neece OA. 2004. Knowledge reuse for innovation. Management Science 50(2): 174-188.
50. Marakas G, Elam J. 1998. Semantic structuring in analyst acquisition and representation of facts in requirement analysis. Information Systems Research 9(1): 37-63.
51. Mattessich PW, Murray-Close M, Monsey BR. 2001. Collaboration: What Makes It Work. Amherst H. Wilder Foundation: Saint Paul, MN.
52. McAllister D. 1995. Affect- and cognition-based trust as foundations for interpersonal cooperation in organizations. Academy of Management Journal 38(1): 24-59.
53. McEvily B, Perrone V, Zaheer A. 2003. Trust as an organizing principle. Organization Science 14(1): 91-103.
54. Mishra AK. 1996. Organizational responses to crisis: the centrality of trust. In Trust in organizations: Frontiers of theory and research, Tyler T, Kramer RM (eds). Sage: Thousand Oaks, CA; 261-287.
55. Neill CJ, Laplante PA. 2003. Requirements engineering: the state of the practice. IEEE Software 20(6): 40-45.
56. Polanyi M. 1966. The Tacit Dimension. Doubleday: Garden City, NY.
57. Powell W. 1996. Trust-based forms of governance. In Trust in Organizations: Frontiers of Theory and Research, Tyler T, Kramer RM (eds). Sage: Thousand Oaks, CA; 51-67.
58. Powell W, Koput KW, Smith-Doerr L. 1996. Interorganizational collaboration and the locus of innovation: networks of learning in biotechnology. Administrative Science Quarterly 41(1): 116-145.
59. Preston AM. 1991. The "Problem" in and of management information systems. Accounting, Management, and Information Technology 1(1): 43-69.
60. Raffo DM, Kellner M. 2000. Empirical analysis in software process simulation modeling. Journal of Systems and Software 53(1): 31-41.
61. Richardson GP, Andersen DF. 1995. Teamwork in group model building. System Dynamics Review 11(2): 113-137.
62. Richardson GP, Pugh AL III. 1981. Introduction to System Dynamics Modeling with Dynamo. Productivity Press: Cambridge, MA. (Now available from Pegasus Communications, Waltham, MA).
63. Roberts EB. 1974. A simple model of R&D project dynamics. R&D Management 5(1): 1-15.
64. Rodrigues AG, Williams TM. 1998. System dynamics in project management: assessing the impacts of client behaviour on project performance. Journal of Operational Research Society 49(1): 2-15.
65. Rousseau DM, Sitkin SB, Burt RS, Camerer C. 1998. Not so different after all: a cross-discipline view of trust. Academy of Management Review 23(3): 393-404.
66. Sabherwal R. 1999. The role of trust in outsourced IS development projects. Communications of the ACM 42(2): 80-86.
67. Sachs P. 1995. Transforming work: collaboration, learning and design. Communications of the ACM 38(9): 36-44.
68. Saiedian H, Dale R. 2000. Requirements engineering: making the connection between the software developer and customer. Information and Software Technology 42(6): 419-428.
69. Sambamurthy V, Kirsch LJ. 2000. An integrative framework of the information systems development process. Decision Sciences 31(2): 391-411.
70. Sheppard BH, Sherman DM. 1998. The grammars of trust: a model and general implications. Academy of Management Review 23(3): 422-437.
71. Sommerville I, Sawyer P. 1997. Requirements Engineering: A Good Practice Guide. Wiley: Chichester.
72. Stallinger F, Grünbacher P. 2001. System dynamics modelling and simulation of collaborative requirements engineering. Journal of Systems and Software 59(3): 311-321.
73. Star SL. 1989. The structure of ill-structured solutions: boundary objects and heterogeneous distributed problem solving. In Distributed Artificial Intelligence, Gasser L, Huhns MN (eds). Morgan Kaufmann: San Mateo, CA; 37-54.
74. Star SL, Griesemer JR. 1989. Institutional ecology, "translations" and boundary objects: amateurs and professionals in Berkeley's Museum of Vertebrate Zoology. Social Studies of Science 19(3): 387-420.
75. Sterman JD. 1992. System dynamics modeling for project management. MIT: Cambridge, MA.
76. Sterman JD. 2000. Business Dynamics: Systems Thinking and Modeling for a Complex World. Irwin/McGraw-Hill: Boston, MA.
77. Suchman L. 1988. Representing practice in cognitive science. Human Studies 11(2/3): 305-325.
78. Szulanski G. 2000. The process of knowledge transfer: a diachronic analysis of stickiness. Organizational Behavior and Human Decision Processes 82(1): 9-27.
79. Uzzi B. 1997. Social structure and competition in interfirm networks: the paradox of embeddedness. Administrative Science Quarterly 42(1): 35-67.
80. Van Lamsweerde A. 2000. Requirements engineering in the year 00: a research perspective. In Proceedings of the 22nd International Conference in Software Engineering, Limerick, Ireland.
81. Vangen S, Huxham C. 2003. Nurturing collaborative relations: building trust in interorganizational collaboration. Journal of Applied Behavioral Science 39(1): 5-31.
82. Vennix JAM. 1999. Group model-building: tackling messy problems. System Dynamics Review 15(4): 379-401.
83. Watson HJ, Frolick MN. 1993. Determining information requirements for an EIS. MIS Quarterly 17(3): 255-269.
84. Wenger E. 1998. Communities of Practice: Learning, Meaning and Identity. Cambridge University Press: Cambridge, U.K.
85. Wetherbe JC. 1991. Executive information requirements: getting it right. MIS Quarterly 15(1): 51-66.
86. Yourdon E. 2004. Death March. Pearson Education: Upper Saddle River, NJ.
87. Zand DE. 1972. Trust and managerial problem solving. Administrative Science Quarterly 17(2): 229-239.
88. Zhang J. 2003. Cross-boundary knowledge sharing: a case study of building the multi-purpose access for customer relations and operational support (macros) system. PhD dissertation, School of Information Science and Policy, University at Albany: Albany, NY.