Versions Compared

Old Version 12

changes.mady.by.user Allison Costa

Saved on

compared with

New Version 13

changes.mady.by.user Allison Costa

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Attendance:

Agenda:

  • Mark F -
  • From Backlog 1/23/23
    • Confirmed removing "Closed" as a Review State in favor of just deleting the ISR.
    • Confirmed removing "None" as a Review Type
    • ISRs are created upon the assignment of a Review Type (Primary, Secondary, Tertiary)
    • If the Review Type is unassigned, then the ISR is deleted.
    • A SRP Chair or TTA member has the ability to change the Review Type.
      • If the Review State is not blank, then a warning is given saying that data (ISR) will be deleted
      • If the Review State is Finalized, then the Review Type cannot be changed by either TTA or SRP Chair.
  • Discussion on stories in Sprint 47
    • As written, are these capturing where (e.g., FE/BE) and what (e.g., requirements) the work currently is?


Expand
titleConfirm Conflict Certification (done?)

Jira
showSummaryfalse
serverDMS JIRA
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdeb2e750b-a83a-387e-8345-36eee8a98f01
keySTT-1146

  • SRP Member action and TTA Group member powers

  • For a SRP member, they would not have a “save” option on conflict certification. They can only certify or the changes do not persist.

  • A TTA member should be able to change a conflict designation at any time. We do not need the software to manage if it is the result of the auto conflict process or a user specified conflict, as we trust the TTA member.

  • A TTA member should be able to certify a user's conflict status, if necessary.
Expand
titleMapping Requirements to Jira Stories (Allie)

688-TTAT-014-MGMT_REQ-Mapped-Jira-1-20-23.csv

Image Removed

  • General nomenclature:
    • The top level requirement for the TTAT project is TTA-1.
    • The lower level requirements are listed as TTA-L0 and -L1. They are subdivided further by number (e.g., TTA-L0-2) in the requirements doc but consolidated as to be TTA-L0 and -L1 here
      • L0 are Science Requirements or Stakeholder Requirements.
      • L1 are System Level Requirements.
    • SRDP derived requirements are marked as TTA-SRDP.
  • Procedure:
    • Map the stories from Jira to the requirements and rate, on a scale of 0 - 5 how well the stories met the requirement.
    • 0 - The requirement is no longer a requirement.
      • TTA-L1-80: History of the changes made during the consensus review need to be tracked.
      • TTA-L1-29: It shall be possible  with best efforts  to create a new draft from a proposal in the WITHDRAWN or COMPLETED state.
    • 1 - The requirement does not need a story to explicitly be satisfied.
      • TTA-L1-94: In the rare case that a reviewer feels uncomfortable reviewing a proposal they will communicate outside the TTA Tools to a TTA Group member to reassign the review.
    • 2 - There is not a story that addresses the requirements.
    • 3 - There is at least one story that addresses the requirement but it is very insufficient in scope.
    • 4 - There is at least one story that addresses the requirement but not fully.
    • 5 - There is at least one story that meets or exceeds the scope of the requirement.

Image AddedImage Removed






Open Actions:

Task report
pages68321335