Moving into a new software project landscape

ABSTRACT

When developers join a software development project, they find themselves in a project landscape, and they must become familiar with the various landscape features. To better understand the nature of project landscapes and the integration process, with a view to improving the experience of both newcomers and the people responsible for orienting them, we performed a grounded theory study with 18 newcomers across 18 projects. We identified the main features that characterize a project landscape, together with key orientation aids and obstacles, and we theorize that there are three primary factors that impact the integration experience of newcomers: early experimentation, internalizing structures and cultures, and progress validation.

References

1. A. Begel and B. Simon. Novice software developers, all over again. In Proceeding of the fourth international workshop on Computing education research, pages 3--14, 2008.
2. A. Begel and B. Simon. Struggles of new college graduates in their first software development job. In Proceedings of the 39th SIGCSE technical symposium on Computer science education, pages 226--230, 2008.
3. L. M. Berlin. Beyond program understanding: A look at programming expertise in industry. In Empirical Studies of Programmers - Fifth Workshop, pages 6--25, 1993.
4. J. Corbin and A. C. Strauss. Basics of Qualitative Research: Techniques and Procedures for Developing Grounded Theory. Sage Publications, 3rd edition, 2007.
5. J. W. Creswell. Qualitative Inquiry and Research Design. Sage Publications, 2nd edition, 2007.
6. B. Dagenais, H. Ossher, R. K. E. Bellamy, M. P. Robillard, and J. P. de Vries. A qualitative study on project landscapes. In Cooperative and Human Aspects of Software Engineering, an ICSE workshop, pages 32--35, 2009.
7. C. R. B. de Souza and D. F. Redmiles. An empirical study of software developers' management of dependencies and changes. In Proceedings of the 30th international conference on Software engineering, pages 241--250, 2008.
8. S. C. B. de Souza, N. Anquetil, and K. M. de Oliveira. A study of the documentation essential to software maintenance. In Proceedings of the 23rd annual international conference on Design of communication, pages 68--75, 2005.
9. G. R. Jones. Socialization tactics, self-efficacy, and newcomers' adjustments to organizations. Academy of Management Journal, 29(2):282--279, 1986.
10. M. S. Knowles. The Adult Learner: A Neglected Species. Gulf Publishing Co, 4th edition, 1990.
11. A. J. Ko, R. DeLine, and G. Venolia. Information needs in collocated software development teams. In Proceedings of the 29th international conference on Software Engineering, pages 344--353, 2007.
12. T. C. Lethbridge, J. Singer, and A. Forward. How software engineers use documentation: the state of the practice. IEEE Software, 20(6):35--39, 2003.
13. S. Newell and R. Galliers. Knowledge transfer: Short-circuiting the learning cycle? In Proceedings of the 39th Annual Hawaii International Conference on System Sciences, pages 149--b, 2006.
14. J. Sillito, G. C. Murphy, and K. D. Volder. Asking and answering questions during a programming change task. IEEE Transactions Software Engineering, 34(4):434--451, 2008.
15. S. E. Sim and R. C. Holt. The ramp-up problem in software projects: a case study of how software immigrants naturalize. In Proceedings of the 20th international conference on Software engineering, pages 361--370, 1998.
16. G. von Krogh, S. Spaeth, and K. R. Lakhani. Community, joining, and specialization in open source software innovation: a case study. Research Policy, 32(7):1217--1241, 2003.