2017-04-25 Meeting Notes

Owned by Christine Di Bella
Last updated: Nov 02, 2021 by Randy Kuehn
3 min read

Date

Call-in Number

1-888-354-0094
Access code is 731627#

Attendees


Boards

Discussion items

TimeItemLed byNotes
5 minRoll callJason Loeffler
20 min Process discussion: prioritizating new JIRA tickets

Jason Loeffler

Christine Di Bella

Laney McGlohon

Background: Prioritization ensures that newly received development items are evaluated in a timely fashion, and that it is always clear which tickets in the backlog are most pressing. While the pace of development varies depending on a number of factors including program staffing, financial resources and community involvement, we want to make sure that tickets are always ready when developers are available to work on them and that it’s clear which are considered most essential to address. We expect that we will usually have multiple streams of development, including program team members, contractors and community developers. The program will aim to use its own resources to assign developers to the tickets ranked highest. We expect that community developers may sometimes work out of priority order, based on what is most important for their home institution or most appealing to them in terms of their skills and interests, but will encourage reference to the prioritization queues when people ask about contributing development effort.


Tickets with a status of Awaiting Prioritization have already been vetted by the program team. During prioritization meetings, the subteam will discuss each ticket with this status, add additional labels if needed, determine if additional information is needed for the ticket to be ready for a developer, and change its status as appropriate. The subteam will rank all tickets it has changed to Ready for Implementation status within their respective queues (bug or feature). Tickets that are considered highest priority will be given the hudson_molonglo label, indicating that we consider them a priority for use of the highest level of program resources. Prioritization will involve continually updating these queues based on the most current information.

Some key points to address in the process discussion:

  • Bug vs. feature queue

  • Choice of statuses and what they mean

  • What goes into ranking within a queue

    • In the case of a bug

      • Is it a blocker or critical?

      • If not, to what degree does it impede use of the application?

      • Is it clear what needs to be done to fix it?  (If not, ticket needs to be updated with this information.)

      • How complex is it to address?

      • Are there other related bugs that should be addressed in concert?

    • In the case of a feature

      • How prevalent is the need? (i.e. Is it a request based on a single or small number of institutions’ workflows or does it reflect wider practice?)

      • Does it purely add functionality or does it change existing functionality? If it changes existing functionality, to what degree will it impact people who are using/have built workflows around the existing functionality? Does it need wider community discussion or review?

      • How clear is it what needs to be done to implement it? If it requires a specification, how complete is the specification?

      • Is there other work planned that will affect it?
5 minConferencing technology for future meetingsJason Loeffler
  • For future meetings, we would like to use a video conferencing option to allow people to share screens during the priorization process. Is there anything that people have access to and particularly like?
25 minReview of new* Awaiting Prioritization ticketsJason Loeffler

  • For this meeting “new” refers to tickets received since the last regular prioritization session in November. Once we’ve caught up with these, “new” will be only tickets received since the last meeting.

5 minOther discussionAs needed

Action items

  •