well in my opinion there need not be so much difference between the two.
There would naturally be more focus on testing for a maintenance team, but optimally development should be executed in much the same way regardless of the type of project.
A change is a change, whether pertaining to enhancements, modifications or new development at the one end, and error correction focused changes for a maintenance project at the other end.
Important is to define the outcome of the project; new releases in ever so small steps for maintenance should definitately be handled in the same manner as larger iterations or releases resulting from new development.
There might be differences in the rolls you link to a development project, versus the maintenance project, and the activities might be focused more on enhancement than on corrections, and vice versa.
But, the method you follow should, in principle, not differ IMHO between the two development aspects.
Record and monitor each change, preferably in a change management system, and link these changes to the source code database and SCM-tool.
This way there is really no difference in methods, but merely in staffing.