Versions Compared

Version Old Version 4 New Version 5
Changes made by

Holly Mistlebauer

Holly Mistlebauer

Saved on

Key

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

Date

26-July-2021

Attendees

...

30 minutes maximumApprovals for R1 2021 Hot Fixes

Questions to answer:

  1. What is issue?
  2. How many people are impacted?
  3. What is effort to fix it?
  4. What will it take to test the fix?


10 minutes maximumStatus update
Oleksii Petrenko


UXPROD-3104 (Fail renewal for inactive or expired user and allow override)

Holly MistlebauerThe lack of this feature is causing issues for Cornell.  It seems like we should already be blocking at least expired these patrons from renewing.  Is there any way this work can be included in the Kiwi release.  The long-term solution is UXPROD-3104.  We have come up with a thin-thread that is described in new tickets  CIRC-1187 and UIU-2229.  Is it o.k. for Prokopovych to do this work for Kiwi?

Continue discussion of JIRA Issue Type "Bug"

Holly Mistlebauer

Issues related to what we define as a "bug"...

  • Historically, I have created bugs in situations where I (as PO) made a mistake in a user story by overlooking something or stating something incorrectly.  I believe the the PO is part of the dev team, so POs are the cause of bugs too. 
  • The devs don't want PO bugs to count against them because they are "graded" based on the number of bugs they have. 
  • POs need these to be bugs because only a bug can be part of a bugfix/hotfix release. 

This issue was discussed ages ago, along with the possibility of making a new JIRA Issue Type for PO bugs.  I'm not sure that is the answer.  Perhaps we need to stop "grading" the teams on bugs?  We have situations where the dev team that caused the bug is not the dev team that fixes the problem.  This also counts "against" the dev team that fixes the bug.

(See Cate's document)

Need to discuss further.  Some ideas/questions from last meeting...

  • No public statistics?  We don't need to compare teams with stats that have no context.  Comparing teams is anti-Agile.
  • Find other ways of measuring team success in a non-public way.
  • Share information about the "spirit" behind the statistics.  No intention to shame specific teams.
  • Share information about
  • What are we actually doing with statistics?  Who is doing something with this information?

...