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. Product Lifecycle
  3. Application Lifecycle
  4. Change & Release Management - legal, compliance or audit requirements

Change & Release Management - legal, compliance or audit requirements

Scheduled Pinned Locked Moved Application Lifecycle
businesshelpquestiondiscussionannouncement
3 Posts 3 Posters 2 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.
  • P Offline
    P Offline
    pkaelin
    wrote on last edited by
    #1

    Has anyone some experience when it comes to change & release management and legal, compliance or audit requirements (country dependent)? Can you share some of your legal (country dependent), compliance or audit requirements? We already have a very basic directive from legal and compliance to follow but I am curious what other people do or don’t do. By the way my goal is to have the leanest/simplest change & release process one can think of but still have an audit trail. Like create an issue tracking item (request of change) with required fields, status, workflow and linked work orders including linked stories. I already have it all planned out but I would like your input for comparison/improvements. Discussion examples: what to do when the location of the data changes, shall we have sign-offs or not, do we need work orders, do we need linked stories, which fields are important/required etc.

    PKaelin

    M B 2 Replies Last reply
    0
    • P pkaelin

      Has anyone some experience when it comes to change & release management and legal, compliance or audit requirements (country dependent)? Can you share some of your legal (country dependent), compliance or audit requirements? We already have a very basic directive from legal and compliance to follow but I am curious what other people do or don’t do. By the way my goal is to have the leanest/simplest change & release process one can think of but still have an audit trail. Like create an issue tracking item (request of change) with required fields, status, workflow and linked work orders including linked stories. I already have it all planned out but I would like your input for comparison/improvements. Discussion examples: what to do when the location of the data changes, shall we have sign-offs or not, do we need work orders, do we need linked stories, which fields are important/required etc.

      PKaelin

      M Offline
      M Offline
      Member 15252162
      wrote on last edited by
      #2

      Enroll for the best GST practitioner certification course. This 4 weeks of live online https://iimskills.com/gst-certification-course/GST Certification Course which includes practical assignment, hands-on learning, freelance opportunities, dedicated placement cell, free ebooks and more.

      1 Reply Last reply
      0
      • P pkaelin

        Has anyone some experience when it comes to change & release management and legal, compliance or audit requirements (country dependent)? Can you share some of your legal (country dependent), compliance or audit requirements? We already have a very basic directive from legal and compliance to follow but I am curious what other people do or don’t do. By the way my goal is to have the leanest/simplest change & release process one can think of but still have an audit trail. Like create an issue tracking item (request of change) with required fields, status, workflow and linked work orders including linked stories. I already have it all planned out but I would like your input for comparison/improvements. Discussion examples: what to do when the location of the data changes, shall we have sign-offs or not, do we need work orders, do we need linked stories, which fields are important/required etc.

        PKaelin

        B Offline
        B Offline
        bahary kor
        wrote on last edited by
        #3

        AIs should have formal change management procedures to keep their BCPs updated in respect of any relevant changes with proper approval and documentation.GAMEFOWL FOR SALE | Gamefowl Eggs For Sale[^]

        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