Quick update: I’ve recently completed a project where I was brought in to review what was currently there, figure out how to solve email issues, hire two developers to work as contractors on the project, then project manage as much as needed to get it done on time and in budget (as usual), for a project delivered in 3 languages.

So the project looked as follows:

1. Review codebase
2. Review problems with mail delivery
3. Suggest improvements, scope and people needed to bring the project in under budget
4. Do interviews for technical people (ended up interviewing 6 people in a day for 2 roles)
5. Get all code under control, install code revision and management, get developers working on new version of project
6. Implement email fixes to get email into Inboxes
7. Project manage for weekly updates to client

One of the things that made the project manageable from my perspective was hiring the right people from the beginning, so that my work was limited to communication and prioritisation, which is how it should be. My general point of view is that if a product or project manager is spending more than 20% to 30% of their time on any one project, then something is wrong. Maybe 40% on the outside is acceptable for a really technical project, or one heavy in stakeholder communication, but then that’s really becoming an account director or similiar.

So, once the tech people were bedded down and we’d established the priorities for the project, we moved into a nice agile routine which got the project done well under time, making the client happy. Principle lesson and take away – hire the right people from the beginning, and life is easy. Do the opposite, and projects can be hell