It is possible to believe that there is nothing left to be done. That all of the roles outlined thus far is all that is needed to make the process work. However, the role of the development manager is critical to the long-term success of the software development team. The role that the development manager plays – particularly when interacting with the project manager – is essential to a continuously improving process. (If you’ve not been following the series, you might want to read Cracking the Code: Breaking Down the Software Development Roles.)
What’s the Development Manager role?
The development manager’s role can be described as “everything else”. Although accurate this description is not very illuminating.
The development management role is the role whose purpose it is to keep the vision on track. This is much like a CEO, who sets the vision for an organization. This of course differs from the COO, who-like a project manager-ensures the day-to-day operations. While it’s the project manager’s goal to get the project to the finish line, it is the Development Manager ‘s responsibility to look ahead to make sure that the finish line is the right finish line to be reaching. While the project management position is a management position, the development manager role is a leadership position. Click here to see how the the Deployment role fits within the full organizational chart.
Read more of the article at http://www.developer.com/java/ent/article.php/3529081
[Author’s Note: I really enjoyed the mental exercise that writing this series brought. It was a good way for me to clarify my thinking around the various roles in the software development process. I hope that it can provide a framework for understanding how people fit into the process in your organization. The next series is on Coding standards and starts in just a few weeks. I’m always happy to get input on what you think should or shouldn’t be in coding standards.]