A common career progression in computing is to start as a programmer, then become one of several team leaders or junior project managers reporting to a more senior manager, and after that to manage progressively larger projects.
This book is targeted at the team leader or junior project manager getting to grips with the problems of management for the first time. It assumes that the team under your control is quite small (no more than five or six), and there is some more senior guidance and supervision. You may have had a certain amount of management training, but this is by no means always the case, so I don't make too many assumptions.
If you're a more senior manager, or an architect, you should also find something useful in this book (particularly if your own introduction to management was unsupported or informal). The book should clarify your role, may provide some useful ideas and references, and may help if you're involved with a different part of the development life-cycle for the first time.
However, don't expect a wealth of detail on managing large projects. The principles are always the same, but there are methods and tools you can use to manage the volume of information in a large project which are inappropriate for a book of this scope. The "further reading" list may be helpful.
I have tried not to make too many assumptions about the type of systems you're working on, or the languages and methods you use. However, I have to take something as a basis, and I have chosen what I'm most familiar with, which is commercial database systems. These probably represent the bulk of current custom software development, and introduce most of the important management principles. Tve also introduced some of the principles of client-server systems and the differences between building and buying systems, also from my own experience. Again, if you develop embedded or real-time systems, for example, some of your analysis and design methods will be quite different, but the management principles are the same.
This little book can't be a substitute for training, experience, or for the advice and assistance which you should get from more senior colleagues, drawing on their experience. Don't be afraid to ask for help or advice, and take the opportunity of training if it presents itself. Also, you'll probably need to consult other books for the detail of particular methods, techniques and standards. However, I hope my book will provide a sound foundation you can build on as your experience grows.
Was this article helpful?
What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.