Is the sysadmin/netadmin the defacto project planner at your organization?
- by gft74
At my company it has somehow over the past few years slowly become my job to come up with a project plan, milestones and time lines for deployment of developer applications.
Typical scenario:
My team receives a request for a new website/db combo and date for deployment.
I send back a questionnaire for the developer to fill out on all the reqs for the site (ssl? db? growth projections etc.)
After I get back all the information, the head of development wants a well developed document of
what servers will it live on
why those servers
what is the time line for creating the resources
step-by-step SOP for getting the application on the server and all related resources created (dns, firewall, load balancer etc.)
I maybe just whining but it feels like this is something better suited to our Project Management staff (which we have) or to the developer. I understand that I need to give them a time-line on creating the resources, but still feel like this is overkill. We already produce documentation on where everything lives and track configuration changes to equipment.
How do other sysadmin folks handle this?
