A well organized article on IBM developerworks about test management:

http://www.ibm.com/developerworks/rational/library/06/1107_davis/

The takeway I like is:

Testing tasks:

• Organization
• Planning
• Authoring
• Executing
• Reporting

Really not that specific to testing, but helpful to think about when “planning” or “managing” or whatever it is you call it.

I don’t know if I endorse the conclusions or descriptions of the article, but this is a good outline.  I’ll try to elaborate on my “interpretation” of it.