Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Support team hand over plan

Support team hand over plan

Scheduled Pinned Locked Moved IT & Infrastructure
collaboration
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • E Offline
    E Offline
    EvoFreak
    wrote on last edited by
    #1

    Hi, I work on the support team (as a software developer). Thus far I haven't seen from what I have searched on the net, a good support team hand over plan. Basically I would like to know what are the key things that we as the support team members should be looking for, from the project team. Thanks,

    --------------------------------- There is life outside coding.

    P E 2 Replies Last reply
    0
    • E EvoFreak

      Hi, I work on the support team (as a software developer). Thus far I haven't seen from what I have searched on the net, a good support team hand over plan. Basically I would like to know what are the key things that we as the support team members should be looking for, from the project team. Thanks,

      --------------------------------- There is life outside coding.

      P Offline
      P Offline
      Pete OHanlon
      wrote on last edited by
      #2

      Well, a good start would be to get a copy of the acceptance criteria for the project. If you don't know what is being accepted, you won't know what the client is expecting. Obviously, you'll need a copy of the designs, but you should also get information such as release components, version numbers, source repository configuration, configuration settings, project setup files and so on. Ideally, you should have a member of the support team working alongside the development team for a period of time prior to the handover. They would then become the support product "champion".

      Deja View - the feeling that you've seen this post before.

      My blog | My articles | MoXAML PowerToys

      1 Reply Last reply
      0
      • E EvoFreak

        Hi, I work on the support team (as a software developer). Thus far I haven't seen from what I have searched on the net, a good support team hand over plan. Basically I would like to know what are the key things that we as the support team members should be looking for, from the project team. Thanks,

        --------------------------------- There is life outside coding.

        E Offline
        E Offline
        EvoFreak
        wrote on last edited by
        #3

        Anybody else got anything, please?

        --------------------------------- There is life outside coding.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups