Responsibility for Process
Who is responsible for the software team's processes?
In the dynamic world of software development, the question often arises: Who is responsible for the processes of a software development team? The candidates include
Product Manager
Engineering Manager
Engineering Team
Scrum Master
Head of Product
According to conventional wisdom, the ideal scenario is for the entire team to take ownership of its processes. An empowered team, armed with a deep understanding of customer needs and excellent delivery capabilities, actively orchestrates its work and determines the modus operandi to achieve results.
However, the reality often differs from this textbook example, with teams at different levels of maturity. In such cases, an experienced individual who knows the nuances of successful and failed processes from past experience steps in to define the processes. This role can be a product manager, a technical lead, or anyone else with relevant expertise.
Cross-Team Portfolios
The complexity increases when there are multiple teams working on a portfolio of products. To foster collaboration and information sharing, it is beneficial for these teams to adopt similar processes. However, each team must retain a degree of autonomy to tailor the process to its unique needs. These individual adaptations usually occur at an informal level.
In essence, the path to effective software development processes is about recognizing the maturity of your team and tailoring responsibilities accordingly. Whether it's a self-sufficient team driving its own processes, or an experienced leader guiding a less mature team, the key is to adapt and refine processes for optimal results.
What I read
This is a separate section of this newsletter. I will list some of the best articles I have read on the Internet. They may or may not be related to the topic of this article. I will keep a list of the best articles (currently >700) at https://www.digital-product-management.com.
These are today’s picks:
Does pushing for lower estimates make sense? Pushing for a lower dev estimate is like negotiating better weather with a meteorologist.
Calm and optimism in a crisis: Six practices can help leaders build their self-awareness and guide their organizations.
Good & Bad Remote Worker: What are the traits of a good remote worker, and the ones of a bad one?
I don't have experience with software development teams, but I lead multiple teams that use software and systems that I configure and maintain (learning management systems and content development software). I teach everyone how to use the systems and software and communicate what my standards and expectations are. However, I rely on the managers of each team to hold their team to these standards and show them how to exceed them. I've found that if no one is in charge, Administrative Drift sets in pretty quickly.