Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-7501

Define process for verifying quality of "Done" epics

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      We need to define a process that will ensure we properly check quality of epics that are marked "Done". That includes checking if all deliverables are present (eg code written and linked to the epic), the code is properly documented, unit tests are available etc.

        Attachments

          Issue Links

            Activity

            jbecla Jacek Becla created issue -
            jbecla Jacek Becla made changes -
            Field Original Value New Value
            Epic Link DM-7654 [ 26850 ]
            jbecla Jacek Becla made changes -
            Watchers Jacek Becla [ Jacek Becla ] Jacek Becla, Kian-Tat Lim [ Jacek Becla, Kian-Tat Lim ]
            jbecla Jacek Becla made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            jbecla Jacek Becla made changes -
            Status To Do [ 10001 ] In Progress [ 3 ]
            jbecla Jacek Becla made changes -
            Priority Critical [ 2 ] Major [ 3 ]
            jbecla Jacek Becla made changes -
            Status In Progress [ 3 ] To Do [ 10001 ]
            Hide
            jbecla Jacek Becla added a comment -

            It should be done before F17.

            Show
            jbecla Jacek Becla added a comment - It should be done before F17.
            jbecla Jacek Becla made changes -
            Assignee Jacek Becla [ jbecla ] Tim Jenness [ tjenness ]
            jbecla Jacek Becla made changes -
            Team DMLT / Management [ 11402 ] Architecture [ 10304 ]
            Hide
            tjenness Tim Jenness added a comment -

            Me?

            Show
            tjenness Tim Jenness added a comment - Me?
            tjenness Tim Jenness made changes -
            Link This issue is duplicated by DM-7696 [ DM-7696 ]
            Hide
            jbecla Jacek Becla added a comment -

            Why not?

            Show
            jbecla Jacek Becla added a comment - Why not?
            Hide
            tjenness Tim Jenness added a comment -

            Would this be something for DMTN-020 or LDM-492?

            Show
            tjenness Tim Jenness added a comment - Would this be something for DMTN-020 or LDM-492?
            tjenness Tim Jenness made changes -
            Team Architecture [ 10304 ] T/CAMs [ 11400 ]
            tjenness Tim Jenness made changes -
            Assignee Tim Jenness [ tjenness ] Wil O'Mullane [ womullan ]
            Hide
            tjenness Tim Jenness added a comment -

            I have reassigned this ticket to Wil O'Mullane so that he is aware of the issue and so it can be discussed when he arrives.

            Show
            tjenness Tim Jenness added a comment - I have reassigned this ticket to Wil O'Mullane so that he is aware of the issue and so it can be discussed when he arrives.
            Hide
            womullan Wil O'Mullane added a comment -

            This should be in in Software Product Assurance Document - I suggest we update LSE-13 even if we add a specific DM part .

            Show
            womullan Wil O'Mullane added a comment - This should be in in Software Product Assurance Document - I suggest we update LSE-13 even if we add a specific DM part .
            Hide
            womullan Wil O'Mullane added a comment -

            DMTN-020 section 9.2.2. gives good guidelines on how an pic should be written including "a clearly defined deliverable".

            It is the responsibility of each TCAM to check these deliverables are available (link to code repo/tech note/test report) when closing the ticket.

            It is the responsibility of the DMPM to verify this is actually done consistently. I have to date not being systematically doing this but rather on a spot check basis.

            I will update section 4 of LDMP-294 to reflect the above policy of epic verification. I will undertake to do that more systematically.

            Show
            womullan Wil O'Mullane added a comment - DMTN-020 section 9.2.2. gives good guidelines on how an pic should be written including "a clearly defined deliverable". It is the responsibility of each TCAM to check these deliverables are available (link to code repo/tech note/test report) when closing the ticket. It is the responsibility of the DMPM to verify this is actually done consistently. I have to date not being systematically doing this but rather on a spot check basis. I will update section 4 of LDMP-294 to reflect the above policy of epic verification. I will undertake to do that more systematically.
            swinbank John Swinbank made changes -
            Team T/CAMs [ 11400 ] System Management [ 12217 ]
            Hide
            gpdf Gregory Dubois-Felsmann added a comment -

            See DM-13088; can this ticket be closed with a change to LDM-294 only, or is other work still required? (E.g., Wil mentioned the semi-defunct LSE-13 above.)

            Show
            gpdf Gregory Dubois-Felsmann added a comment - See DM-13088 ; can this ticket be closed with a change to LDM-294 only, or is other work still required? (E.g., Wil mentioned the semi-defunct LSE-13 above.)
            gpdf Gregory Dubois-Felsmann made changes -
            Link This issue relates to DM-13088 [ DM-13088 ]
            Hide
            swinbank John Swinbank added a comment -

            I think that the LDM-294 update is all that's really required here.

            I also think this ticket is much less important than it used to be given LDM-503 and our new approach to testing. The fundamental way we'll know if the work is on track is by completing milestones, rather than by reviewing the contents of epics.

            Show
            swinbank John Swinbank added a comment - I think that the LDM-294 update is all that's really required here. I also think this ticket is much less important than it used to be given LDM-503 and our new approach to testing. The fundamental way we'll know if the work is on track is by completing milestones, rather than by reviewing the contents of epics.
            Hide
            womullan Wil O'Mullane added a comment -

            LDM-294 merged to draft .. will make new release. That plus LDM-503 address this issue

            Show
            womullan Wil O'Mullane added a comment - LDM-294 merged to draft .. will make new release. That plus LDM-503 address this issue
            womullan Wil O'Mullane made changes -
            Resolution Done [ 10000 ]
            Status To Do [ 10001 ] Done [ 10002 ]

              People

              • Assignee:
                womullan Wil O'Mullane
                Reporter:
                jbecla Jacek Becla
                Watchers:
                Gregory Dubois-Felsmann, Jacek Becla, John Swinbank, Kian-Tat Lim, Tim Jenness, Wil O'Mullane
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Summary Panel