Child pages
  • Sprint 306

Versions Compared

Key

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


Date

Participants



Sprint Review

  • Complete sprint
  • Determine if sprint goals were met
  • Discuss completed items
    • Demo any necessary items
  • Decide what to do with any item not completed

Jira
serverSSDT JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerysprint = "305" ORDER BY fixVersion
serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca

Support Team Discussion Items

  • ()

Technical Discussion Items

  • ()

Retrospective

Review prior retrospective (Sprint  305)

Play Start, Stop, Continue

https://trello.com/b/N9kL6td2

About this sprint: 


Panel
borderColor#91c89c
bgColor#f3f9f4

What did we do well / What did we learn?



Panel
borderColor#d04437
bgColor#fff8f7

What should we have done better?



Panel
borderColor#91c89c
bgColor#f3f9f4

What should we start doing?



Panel
borderColor#d04437
bgColor#fff8f7

What should we stop doing?



Panel
borderColor#334C80
bgColor#F0F5FF

What should we keep doing?


Actions

  •   

Developer Discussion Items

  1. (Justin) 
    Jira
    serverSSDT JIRA
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSPSR-3624
     warning or error?
    1. Producing a warning should be ok for now
  2. (Justin) UAT - Should docks on advanced compensations even be allowed?
  3. (Andy) UAT - Should advance reports be disabled while in advance?  Currently the button to generate a submission file is disabled while in advance, but the report buttons remain enabled.
    1. Discussed with UAT - Issue added
    2. Jira
      serverSSDT JIRA
      serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
      keyUSPSR-5036
  4. (davis) 
    Jira
    serverSSDT JIRA
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSPSR-5018
    1. Discussion on the account sync issue
  5. (Justin) UAT - Should users be able to manually turn advance mode on/off in the configuration?
    1. Discussed with UAT, will look into making this prop read only if NOT in advance mode
  6. (davis) Audit Report discussion
    1. Per priority committee, the Audit report will be moved to 6.11.0 - 6.12.0
  7. (davis) 
    Jira
    serverSSDT JIRA
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSPSR-5031
  8. (Greg) Ticket came in where user was unable to add a Contract compensation manually via Current due to a 'unit amount cannot be zero' error.  Turns out there was an archived NonContract compensation that was actually the source of the error.  Should we ignore archived compensations?  Or at the very least, give preference to non-archived compensations?
  9. (Greg)  Both Ryan McClay and myself have noticed error messages in the server logs that seem problematic to me: 
    Jira
    serverSSDT JIRA
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSPSR-5033
  10. (Greg) Do we need to provide a way for USPS-only districts to bypass the externalId validation?  
    Jira
    serverSSDT JIRA
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSPSR-5038
  11. (Andy) Soap bridge - queryPositionsById - supposed to return all positions for a given employee number that is passed in as a parameter.  Currently uses a 'like' query to find positions with position.employee.number like the passed number.  If a number such as '2233' is passed in and there is an employee with number = 2233 and also an employee with number = 22334455, positions for both employees are returned.  A kiosk district reported that a situation similar to this resulted in not all positions showing up for the employee with the 2233 number.  The kiosk apparently does not cope with positions for multiple employees being returned by this soap call.  They are expecting only positions for the employee who's number they provide.  We would need to update the soap bridge method to use = instead of 'like'
    1. This is currently preventing one employee from submitting leave in the kiosk.  Informed the kiosk developers of what we are currently returning and told them they could search the results for the correct employee.  They are not making the update at this point because they believe our service is returning incorrect results.
    2. Issue added
    3. Jira
      serverSSDT JIRA
      serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
      keyUSPSR-5047
  12. (Justin) Tax Estimator
    Jira
    serverSSDT JIRA
    serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca
    keyUSPSR-5002
      - Handling multiple compensations with different retirements or a job with no retirement

Plan Sprint

  • Average velocity for USPS-R team: 8 story points
  • Clarify team availability 
  • Add user stories and bugs to the next sprint
  • Make sure each story / bug is clear 
  • Estimate each story / bug
  • Create sprint goal
  • Start sprint

Jira
serverSSDT JIRA
columnskey,summary,type,assignee,priority,status,fixversions,story points
maximumIssues1000
jqlQuerysprint = "306" ORDER BY fixVersion
serverId925ea1db-0df8-3e91-bcfb-6b1c8a04f6ca