I am a one-man IT department for a small company in Vermont. Though my title is IT Director, I do it all. I have a side project for one of our clients to do (a Flash feasiblility study) an I was told that "all company work comes first." However, taking this advice realistically means that I will never get to the client's project. I recently made a list of my current projects (mostly datbase development and coding, debugging, etc for a web-based application we produced) and other ongoing IT duties (network maintenance, backups, etc). We are also setting up an offsite disaster recovery location with full redundancy and failover for our web apps and database. There is a lot to do.
In my attempt to get these projects organized, I input all of these projects into MS Project (its what I have). I broke eahc project down in to sub-parts and linked them properly. However, right now the projects are in MS Project as if they were all going to be done concurrently. A few of them can wait until others are done but most of them need to be in work at the same time (e.g. one of our in-house programming projects AND the client's project AND the disaster recovery project). However, since I am the only resource available to be added to any of these projects, I am torn (no pun intended) on how to make sure that the projects get worked on simultaneously. Should I devote certain days of the week to certain projects? I already write Mondays off because of meetings and organization. If I go this route I have no idea how to code this into MS Project so I can give management a realistic view of my schedule. I would love to show them that there is too much work for me to do and give them a reason on paper to hire additional personnel.
Any advice is welcome.
In my attempt to get these projects organized, I input all of these projects into MS Project (its what I have). I broke eahc project down in to sub-parts and linked them properly. However, right now the projects are in MS Project as if they were all going to be done concurrently. A few of them can wait until others are done but most of them need to be in work at the same time (e.g. one of our in-house programming projects AND the client's project AND the disaster recovery project). However, since I am the only resource available to be added to any of these projects, I am torn (no pun intended) on how to make sure that the projects get worked on simultaneously. Should I devote certain days of the week to certain projects? I already write Mondays off because of meetings and organization. If I go this route I have no idea how to code this into MS Project so I can give management a realistic view of my schedule. I would love to show them that there is too much work for me to do and give them a reason on paper to hire additional personnel.
Any advice is welcome.