Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

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?

share|improve this question

migrated from superuser.com Mar 18 '10 at 10:11

This question came from our site for computer enthusiasts and power users.

1 Answer 1

I think you are probably the most qualified person in the organization to answer those questions. The developers will at best tell you what kind of servers they expect an application to need, but not which actual servers to use and how to plug them in. And the project management is mainly only tracking that the documentation is written, but they won't write them.

Now maybe writing the actual documentation isn't the most fun for everyone, but I would embrace the opportunity to be able to plan such things instead of just being told.

share|improve this answer
Yeah, you may want to engage the PM team to help you, maybe train you a bit on some advanced PM tricks - but if you're owning the applications after they're deployed, you should be happy to be able to run the deployment as well. It's better than the alternative. –  mfinni Mar 18 '10 at 13:14

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.