One thing that is inevitable in software development is that you will create bugs in your software. The question becomes how and when you deploy fixes for them. Each client has differing levels of change control processes that need to be considered when dealing with these fixes. You want to eradicate the bugs as quickly as possible, particularly if they are preventing the end users from completing their work, but you don't want to affect current main line development. I'll give you a process I use that seems to be working best after much trial and error.
In the previous blog post, I tried to explore ideas and questions that help me determine how to correct or establish a good domain model. In this second part, I'm writing about the process of implementing those changes as compared to traditional application development.