What counts as software process? Negotiating the boundary of software work through artifacts and conversation

Computer Supported Cooperative Work

Volumn 18, Issue 5-6, 2009, Pages 401-443

  Cohn, Marisa Leavitt ^a   Sim, Susan Elliott ^a   Lee, Charlotte P ^b  

^a Ringgold Standard Institution Informatics   (United States)

^b UNIVERSITY OF WASHINGTON   (United States)

Author keywords

Agile software development; Collaboration; Negotiation; Requirements documentation; Software process models and enactments; Work artifacts

Indexed keywords

AGILE SOFTWARE DEVELOPMENT; COUNTS-AS; DOCUMENTATION OF SOFTWARE; EMPIRICAL FINDINGS; FIELD STUDIES; GENERATIVE SYSTEMS; SOFTWARE DEVELOPER; SOFTWARE DEVELOPMENT; SOFTWARE PROCESS; SOFTWARE PROCESS MODELS;

SOFTWARE DESIGN;

COMPUTER SOFTWARE;

EID: 73449140734     PISSN: 09259724     EISSN: 15737551     Source Type: Journal    
DOI: 10.1007/s10606-009-9100-4     Document Type: Article

References (28)

1. JP Bansler K Bødker 1993 A reappraisal of structured analysis: design in an organizational context ACM Transactions on Information Systems 11 2 165 193 10.1145/130226.148055 (Pubitemid 23650498)
2. Beck, K. (2000). Extreme programming explained: Embrace change. Boston: Addison-Wesley Professional.
3. Bertelsen, O. W., & Bødker, S. (2002). Interaction through clusters of artefacts. 11th European Conference on Cognitive Ergonomics.
4. Boehm, B. (1981). Software engineering economics. Englewood Cliffs: Prentice-Hall.
5. Bourdieu, P. (1977). Outline of a theory of practice. Cambridge: Cambridge University Press.
6. Button, G., & Sharrock, W. (1992). The mundane work of writing and reading computer programs. Cambridge: Rank Xerox, EuroPARC.
7. Button, G., & Sharrock, W. (1994). Occasioned practices in the work of software engineers. In M. Jirotka & J. Goguen (Eds.), Requirements engineering: Social and technical issues. London: Academic Press Professional.
8. Cohn, M. (2004). User stories applied: For agile software development. Boston: Addison-Wesley Professional.
9. Dittrich, Y. (2002). Doing empirical research on software development: Finding a path between understanding, intervention, and method development. In Y. Dittrich, C. Floyd, & R. Klischewski (Eds.), Social thinking-software practice. Cambridge: MIT.
10. Feiler, P. H., & Humphrey, W. S. (1993). Software process development and enactment: Concepts and definitions. In Second International Conference on Continuous Software Process Improvement (pp. 28-40).
11. Fuggetta, A. (2000). Software process: A roadmap. In Proceedings of the conference on The Future of Software Engineering (pp. 25-34).
12. Giddens, A. (1979). Chapter 2: Agency, structure. In Central problems in social theory: action, structure, and contradiction in social analysis. University of California Press.
13. C Larman VR Basili 2003 Iterative and incremental software development IEEE Software 36 6 47 56
14. Latour, B. (1986). The powers of association. In Power, action and belief: A new sociology of knowledge (vol. 32, pp. 264-280).
15. CP Lee 2007 Boundary negotiating artifacts: unbinding the Routine of boundary objects and embracing chaos in collaborative work Journal of Computer Supported Cooperative Work 18 3 307 339 10.1007/s10606-007-9044-5 (Pubitemid 46873352)
16. Lofland, J., Snow, D. A., Anderson, L., & Lofland, L. H. (2005). Analyzing social settings: A guide to qualitative observation and analysis (4th ed.). Belmont: Wadsworth.
17. Naur, P. (1992). Computing: A human activity. New York: ACM.
18. Nørbjerg, J., & Kraft, P. (2002). Software practice is social practice. In Y. Dittrich, C. Floyd & R. Klischewski (Eds.), Social thinking-software practice. Cambridge: MIT.
19. Osterweil, L. (1987). Software processes are software too. In Proceedings of the 9th International Conference on Software Engineering (pp. 2-13).
20. DL Parnas PC Clements 1986 A rational design process: how and why to fake it IEEE Transactions on Software Engineering 12 2 251 257
21. BT Pentland MS Feldman 2005 Organizational routines as a unit of analysis Industrial and Corporate Change 14 793 815 10.1093/icc/dth070 (Pubitemid 41600047)
22. Robinson, H., & Sharp, H. (2003). XP culture: Why the twelve practices both are and are not the most significant thing. Salt Lake City: Agile Development Conference.
23. Scacchi, W. (2001). Process models in software engineering. In J. Marciniak (Ed.), Encyclopedia of software engineering (2nd ed.). New York: Wiley.
24. Schwaber, K., & Beedle, M. (2001). Agile software development with SCRUM. Englewood Cliffs: Prentice Hall.
25. Sim, S. E., Alspaugh, T. A., & Al-Ani, B. (2008). Marginal notes on amethodical requirements engineering: What experts learned from experience. In Proceedings of the 2008 16th IEEE International Requirements Engineering Conference (pp. 105-114).
26. SL Star JR Griesemer 1989 Institutional ecology, 'translations' and boundary objects: amateurs and professionals in Berkeley's Museum of Vertebrate Zoology 1907-39 Social Studies of Science 19 387 420 10.1177/030631289019003001
27. D Truex R Baskerville J Travis 2000 Amethodical systems development: the deferred meaning of systems development methods Accounting, Management and Information Technologies 10 1 53 79 10.1016/S0959-8022(99)00009-0
28. van Vliet, H. (2008). Software engineering: Principles and practice (3rd ed.). New York: Wiley.