It’s all about the process
I might be a captain obvious here, but supporting a process for an analyst / pm is a more important, than micromanaging tasks amongst developer pool.
When a new team member steps in, who’s responsibility is to manage development processes, she needs to find how to make business processes inside a company better.
Business processes are evaluated from various points of view, but in a nutshell, aside from developer professionalism, she needs to make sure there’s no room for slowdowns and uncertanties when product passes different stages across different teams. Whether there are delays in communication, or delays of resources for the project, or sick-days, – there should be a correct process to tackle such cases, in order to minimize negative outcome.
There’s always a temptation to micromanage issues, no matter how big the project is and how little time you have. But project manager’s job is to create a process that allows to handle various situations. Once the process has been established – keep an eye on the workflow, so that it doesn’t jump over the fence of how the process should work.
Fencing is the key idea. Micromanagement is bad, if you don’t have a clear process: it’s time consuming, it’s inefficient on a project scale (of course there are exceptions), and most important – micromanagement doesn’t cope with scaling.
So the typical steps to establish a working mechanism is to:
- Create the process
- Adjust it to keep all needed operations inside that process fence
- Make sure operations can connect to each other via unified inputs and outputs
- Optimize the process to allow painless scaling
- Do not pay too much attention to micromanagement 🙂