- Date: //date
- Time: 9:00 ET
- Location: nraozoom04
Attendance:
Agenda:
- Sprint Calendar
- certify v0.1 as finished (ORR)
- Jira tickets with updated acceptance criteria
Expand title List of Stories Phase transition: Review Configuration → Review Process/Individual Reviews
The System Description 3.5.1 Stakeholder usecase 1 discusses access to past disposition letters and conflicts. Is that assessed by an automatic system or via the self declaration? Does it cut their access to the past reviews only or this proposal too?
dsb: we have not fleshed this out but my thinking is that if the SRP member was a reviewer for the past proposal then they could have access to the proposal and disposition letter. Performing another self declaration seems too cumbersome. If they were not an SRP member for the past proposal they could always request info from the TTA group as a last resort (which is what happens now).
Jira showSummary true server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-884 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-882 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-881 SRP Chair
Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-871 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-887 SRP Member
dsb: STT-875 - we should chat about this ticketseems to me that the conflicted proposals should still be listed.
Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-875 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-888 The System Description implies that a user must select either Conflict or Available per proposal. Is this the behavior we want?
dsb: Yes, I think so.
Jira showSummary true server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-885 dsb: STT-877 - in the system description we used "blank" instead of "not saved" for the review state. I do not feel strongly either way but we should be consistent.
Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-877 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-876 dsb: STT-878 - currently valid scores are between 0.1 and 9.9 (inclusive). Also, I am not sure we want to include cues for the individual review. This is meant to be more free form, unlike the consensus review. One could argue otherwise, but I don't think we currently have cues here.
Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-878 If Review Type is None, what is Review State?
dsb: Blank. That is, the Review State does not change.
dsb: STT-873 - seems to me that the conflicted proposals should still be listed.
Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-873 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-879 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-910 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-911 dsb: STT-905 - I think we want to also see the standard deviation of the Mean Normalized Score
Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-905 Can the SRP member do so automatically or must it be enabled by the chair?
dsb: good question. It might be best to only allow the chair to update the Final Normalized Individual Score.
Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-908 Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-909 Other prompts for the consensus review comments?
dsb: yes, we should include (with defaults) the following to the PI comments:
Recommended time: The SRP does not recommend a change to the proposed time request.
Technical issues affecting ranking or recommended time: None.I am not sure we want prompts for the Internal Comments. If there are no comments, and therefore only the cues, then this might be distracting during the TAC meeting. Most should be blank. Maybe remove for now.
Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-903 TTA Member
Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-898 What are the permissions to a reviewer with a Conflict State of Unknown?
dsb: good question. I think the same as conflicted. Also, I do not think we want to "reset" the conflict state. That is, if a reviewer declared a conflict and now decides they are not conflicted, I do not think we want to set the conflict state back to "unknown" and have them redo the conflict declaration. This unnecessarily complicates the process.
Jira showSummary true server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-886 Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-872 Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-907 Feasibility Reviewer
Jira showSummary false server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-892 Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-893 Phase Transition: Individual Reviews → Consensus Reviews
Dana, what information do you want to see in an interface at this stage?
dsb: I prefer a matrix like the Reviews Summary page in the PST that shows the Review Type and Review State.
Jira server DMS JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId eb2e750b-a83a-387e-8345-36eee8a98f01 key STT-933
Open Actions:
- Confluence Page to house v0.1 review Jeff Kern
- v0.1 review document for TTA group Allison Costa
| Task report | ||
|---|---|---|
|