In this paper, we explore how the choices of boundary work in software development influence the team autonomy enacted by team members. Boundary work is when people protect their professional individual autonomy, when they downplay that autonomy to collaborate over professional boundaries, and when they create new boundaries. Team autonomy is here defined as a team using their autonomy to collaborate in deciding their own output. We use an action research design, with varied methodologies carried out through three action cycles. (...) Our findings show that when collective, collaborative boundary work is not performed, a sort of individualized zone occurs where individuals either try to do collaborative boundary work by themselves or seek individual autonomy. We propose that individual autonomy can be divided into professional individual autonomy and situationally dependent individual autonomy. This research contributes theoretically by showing how the absence of collaborative boundary work can lead to an individualized zone. Practically, it can improve team autonomy by enhancing the understanding of why teams should perform collaborative boundary work. The value of the concept of boundary work used in this setting involves studying the intentions for collaboration, not whether collaboration actually takes place. (shrink)