I am excited and terrified (at once hehe) as I have an opportunity as a “jr. project manager” for a web/software developer to take on sr. project management responsibilities. The company is small and I do not have many experienced mentors in the field (there are only two other project managers in separate divisions of the company.
When I first came the place was in chaos. Projects were not hitting their budget mark, and they rarely had concrete deadlines/priorities.
I am trying now to create a process, a series of workflows, and I am defining what a particular project should do/it’s risks/etc in a Project Plan/Project Requirements Document.
Where I am having trouble is priority, scheduling, and the other critical areas of project management.
I know what’s on our plate to do, but it all seems as though we have to do them all now (and we can’t), and too much burden is on my senior developer to help all of the other developers.
I am thinking I might have to create some concrete days for a quick status meeting (every tuesday), and assign workflows directly to team members (now I am sending it to the lead developer, hoping he can advise them on how to do it).
I think these status meetings can be a structured way to shift priority, and I think by directly tasking everyone on the team with parts of the project, based on how we split it up during a kick-off, it takes some pressure off the lead developer.
Is this a good start? I just feel as though I am in over my head and I really like the job but need to get better…fast.