cooperative-software-development
cooperative-software-development copied to clipboard
Organizations: address varying size
It may not be the right place for it, but I would’ve liked to know more about how an organization scales over time. Including this aspect of an organization would allow the reader to understand what it takes for an organization to grow in terms of human capital, revenue, products, and more.
The section where you describe how roles are often merged into individuals seems ripe for elaboration. When you transition from your experience into the concept of how as organizations scale teams become smaller it may be useful to provide some examples of what may drive an organization to scale (and thus teams specialize further). I would anticipate some of the primary drivers of this to be funding (bootstrapping, seed, series (a, b, c, etc), or M&A).
I love how you included the organization size as an important factor that shaped organizations. So one thing that I would like to critique this chapter is to add more details or ways of how the size of organizations affects the cooperations. For example, how does the role of software engineers might differ if he/she works at a larger company comparing to a smaller company? How will these interactions shift the interactions between employers? What could we do as employees in each scenario to demonstrate the company value while achieving the common goal?
I think that discussing about the potential differences in work culture and environment between smaller startups and established tech companies would've been good to add in this chapter, as it relates to various types of organizations.
I think some mention of how each team has to be consistent with company standards and goals, and how teams communicate to make this happen would be a nice addition, especially considering many students in the class may go on to work for a large tech company.
I would've liked the chapter to touch on what the pros and cons are for an individual adopting multiple roles. I could imagine that the obvious cons would be not being able to specialize/focus on a specific role and potentially being overworked but I would also like to see the possible advantages. What do you get when someone is both a software engineer and a designer and how do they fit within the organization?