Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

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?


migration rejected from Jan 22 '15 at 15:46

This question came from our site for computer enthusiasts and power users. Votes, comments, and answers are locked due to the question being closed here, but it may be eligible for editing and reopening on the site where it originated.

closed as primarily opinion-based by HopelessN00b Jan 21 '15 at 22:44

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

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.

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

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