You reach the top of the mountain more easily when you don't have to beg…
In two earlier blog posts I described how we have organized the software development efforts in our company. I wrote about cross-functional teams and matrix management.
This time, I'd like to talk about software maintenance.
I have recognized two lines of thought regarding maintenance:
Personally, I lean towards option 2. And these are my reasons:
So you see… these are the reasons why I am not in favor of separating software development from software maintenance. Except for the size of the work, I don't see much difference between them. And I believe it's a good thing that software developers share responsibilities in doing maintenance on their own applications (and making sure that they are maintainable at all). And given the complexity of maintenance work, it is good always to have the senior developers involved.
Of course, if you have people responsible for both development of new projects and maintenance of old projects, you run into some interesting resource planning issues…
to be continued…
Subscribe to this blog with a reader or by email!
Latest, greatest and favoritest posts:
How to Do Many Projects (Part 2): Matrix Management
How to Do Many Projects with Few People (Part 1)
How to Handle Many Simultaneous Projects