I definitly agree that there needs to be more attention focused on project managment. Not just on this site, but in the development community in general. I have managed a couple projects and thouroughly enjoyed the challenge, though I love doing the design and code bit too. When I was first thrown into project management, I had not a clue as to what to do aside from using common sense. Common sense is quite useful and you can learn a lot from the school of hard knocks, but I have found several books (and other resources) to be quite helpful in learning how to manage projects. Here is my token list of books: Software Requirements AntiPatterns - What not to do...very good Code Complete (Steve McConnell) Testing Computer Software (Cem Kaner) - Testing methodologies After The Gold Rush (Steve McConnell ?) - Good software people/applied sociology book Other good resources: Experienced, successful project managers The Software Engineering Institure at CMU, Capabilities Maturity Model (www.sei.cmu.edu) Microsoft's MS Solutions Framework By recommending these books and resources, I am NOT endorsing going out and reading a bunch of books and completely adopting somebody else's methodology. Rather, I am recommending reading some books, doing some research, and all the while keeping YOUR organization in mind. The idea is that you have to adapt other people's ideas and methodologies to work for you. Other things work for other people and can give you helpful insights into what MAY work for you, but keep in mind that Steve McConnell does not work on your project team. While I believe well-defined processes are an important part of software development, you should not arbitrarily adopt a process and sacrafice your development projects to it. The key is to do what works for you. Note, however, that this does not mean (IMHO) that you should simply adopt an ad-hoc developement process with no structure or definition, but rather to structure your developement process around your organization and circumstances. Chris Cubley