One vital part of project management that is often missed, sadly most often by highly technical folk is the need for communication.
Every project should specifically address communication. At the beginning of a project the PM should consider and write down, who needs to know "stuff" about this project, for each who, what stuff do they need to know and how will they be informed.
Examples are progress and budget reports to business owners, milestones achieved to the client, how you will achieve team co-ordination. Other things to consider before you unleash the programming hordes is how you will address schedule changes (usually for worse), how are you going to tell the client and management early enough for them to handle the business implications. Once you have this sorted for a workplace it is mostly templating and cookie cutting for each new project.
I cannot stress enough how vital it is to include communication as part of your normal PM work. Projects are implemented by technical staff but the owner is the business and they must be able to make business decisions. To make business decisions and to manage business risk, management must have sufficient timely information. As a PM it is your responsibility to ensure that happens.