There is a good book (called Test Process Improvement) that explains this in more detail. After filling out the worksheets, you will know at what level the organization is, and where opportunities exist as well as the order in which to carry out improvements
Modified this post from same thread in the above link.
The book that outlines the TPI model is:
Test Process Improvement by Tim Koomen and Martin Pol. It is basically a checklist that you can use to determine your current process level. Better yet it tells you what to fix and in what order. It is a good starting point that you can map to your specific organization if you are not totally familiar with where to start in an organization with no process.
I wouldn't suggest doing everything it says (keep a rifle handy to prevent your team from stringing you up if you try). At least it gives you some type of priority. I feel the exact level of change is a little off but anyone with some QA experience can see what should be done first.
The book at least gives you what to look for but won't explain the how to of it all. It will tell you that you need to do a risk assessment but won't really tell you how to go about it. Any decent software testing book will explain what the checklist values are looking for. This saves you from having to make up an untried list. You can use other QA reference books to determine how to do things.
I found that Systematic Software Testing by Craig & Jaskiel is a good companion book. Rick Craig (at least at one point) did TPI Model Training Courses here in the states. His book does cover the topics fairly well. I love the TPI Model and use it everywhere I go. You'll find that many companies that think they have a good process fall somewhere between Chaos and Anarchy...8-)
Testing is not an art (that is unless your definition of art includes breaking other "art").