I will start my Top 500 with this short book. It is more like a handbook of practical advice on the basics of project management, the kind that can be useful to reread occasionally.
Here are some points I learned, remembered or rediscovered. First, the questions to answer when defining a project:
- Why is this project needed?
- What will I get as a result of completing it?
- Will there be any additional outcomes?
- Which tasks are explicitly outside its scope?
- Is anything missing? Does it overlap with other projects? Might its boundaries change?
- Could serious problems arise?
- Are there any special requirements imposed by the client or the circumstances?
It sounds obvious and simple, but useful. I will refine the list and add some questions of my own.
A project plan is one of the most important elements of project management. In a sense, it is a list of the problems that need to be solved to complete the project. How to build one:
- Break tasks down into atomic components.
- Estimate how long each task will take.
- Define their sequence.
- Identify the resources needed to carry out the plan.
- Check which resources are actually available.
- Evaluate the resulting plan.
When developing a plan, it is useful to define fixed reference points or milestones that must never move. A particularly useful piece of advice for large projects.
Questions worth asking yourself after a project ends:
- Which practices should I repeat?
- What will I stop doing?
- What will I definitely introduce in the next project?
- Is there anything else I learned that is worth remembering?
Excellent questions. I will put them to use.
My overall impression: a step-by-step guide to project management for beginners, plus a handy reminder for experienced practitioners.