I saw this question that looks very close to mine, but not entirely.

I've been a professional programmer for close to 2 years. The problem is that I'm the only IT staff in a small company and I did not go through code reviews, office politics or anything that I would have faced in a software company - which makes me feel my 2 years is actually less. Now we're working on a new project with developers that are outsourced and I've pushed to project manager.

I do not see myself as one. The new developers are older and more experienced than me. I've tried to create docs to the best of my knowledge with goals, technologies to use, schemas, and such. I'm seeing what they build and I feel like it's taking too long, but I'm not sure if I just program faster or they're just dragging their feet. So it's hard to say this would take a week when I have no real base line.

I'm wondering how can I effectively manage in this type of situation? Tips or examples to get me through this.

  • @JoeStrazzere I have and he tells me I'm skilled enough. I'm not looking to get out of it, but the dynamic is very new to me and I feel uneasy.
    – Nehpets
    Commented Mar 5, 2019 at 19:00

2 Answers 2


As a project manager, your job is not to tell developers how long they will take to finish a task. Your job is to document the progress, communicate the timeline and progress to stakeholders and be clear about whether you are still on time.

I work with a lot of project managers that never wrote a line of code. How do they estimate? They ask developers that are working on the topic and that is all to it, sometimes they get a second opinion from a more senior developer, if they feel they have.

I've tried to create docs to the best of my knowledge with goals, technologies to use, schemas, and such.

I am not sure exactly what kind of docs you are creating, but to me it sounds that you are doing more than what I would expect from a project manager.

E.g. architectural diagrams and technology decisions usually are not made by the project manager, but by an architect or lead developer or by whatever other developer who had time to do so. The project managers job is to make sure there is adequate documentation, not to write all the documents by themselves.

Make sure you serve your different types of stakeholders:

a.) The developers rely on your plan, mostly to know what to do first and who to work on what. You really don't want to make to many decisions there, only the ones that need to be made or ones that have high impact. E.g. you have a code freez1e for your iOS app approaching, this needs to be done first. You haven't made the final decision whether you change DB vendors? Do the DB integration later.

b.) Your customers are more interested in the results, and all they want to know is when you are done and what they will get. except when they want more features faster, which is often the case, and you will have to find a diplomatic answer ;)

c.) Other stakeholders might be teams that have to integrate with the code, other project managers that are waiting for your resources (people) to be free, legal, infrastructure services etc. they are usually interested in specific aspects of your project (e.g. compliance with GDPR, oh fun)

I do not see myself as one. The new developers are older and more experienced than me

You might feel a little bit of self-doubt, when you start thinking of your role as the captain of the football team. If that happens, see yourself as the bus driver. You make sure the team finds their way into the stadium, so they don't have to worry about it and can focus on the game. But it is not necessary that you are an experienced player yourself.

  • 1
    thank you. This is very constructive and I really like thinking myself as a bus driver. I should step back and look at things at a macro level. I would accept / upvote, but cannot currently :/ Thank you again!
    – Nehpets
    Commented Mar 6, 2019 at 16:44

You're doing the job, you're a project manager. You're probably experiencing the less known side of the Dunning-Krueger effect. You're likely more skilled than you think.

There are PLENTY of books out there that you can get the info from, but just start from the simple concepts such as RACI charts, and reporting schedules, simple gannt charts, and build from there. You have time to learn, and room to grow. Google "project management tutorials" for help on finding tutorials like this We all had to start somewhere, don't let a lack of experience intimidate you. You are up to this.

  • I just feel like the techniques used won't be optimized enough given my level of experience. You're correct in that we all have to start somewhere. Thank you.
    – Nehpets
    Commented Mar 5, 2019 at 18:59
  • @Nehpets trust me on this one, I walked in cold as a project manager. ZERO experience. You can do this, check out those links. Commented Mar 5, 2019 at 19:00

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .