Systems Squad Issue Tracking and Scrum

To establish a successful, efficient discussion on technical questions and issues, please check the below guidelines.

Issue tracking

Github Issues page of zowe/zowe-install-packaging repository is the primary place to raise questions and issues.

Scrum Meeting

Please check schedule from OMP zowe-dev Calendar page. Currently, the meeting is scheduled on every Thursday 11 am ET (America/New_York time zone).

Meeting agenda

The meeting agenda is tracked by Github label "scrum discussion" along with priority labels.

The scrum meeting host should share the agenda at the beginning of the meeting and should call out if others have (ad-hoc) topics want to discuss.

Ad-hoc meetings could be suggested and should be published to Slack channels for community awareness.

Agenda priority

To better use of the one-hour meeting, the priority of agenda topics will be managed in such way:

• Topics may have big impacts, especially in the current PI:
  • before LTS, topics which introduce or potentially introduce breaking changes,
  • align to major deliverable planned in current PI,
  • blocking failures, critical security vulnerabilities either identified by Zowe community or users.
• Topics raised by colleagues from Europe or Asia timezone, since the meeting is very late for them.
• Non-blocking failures.
• Good-to-have improvement ideas.
• OK-to-have improvement ideas.
• After LTS, topics that introduce or potentially introduce breaking changes have the lowest priority since it means they can only be introduced in the next LTS.

Adding topics to agenda

Really simple topics can be raised during the meeting. These ad-hoc topics should not be expected to cost over 5 minutes in general. Otherwise, a Github issue is suggested to track the discussion.

Relatively complicated topics, a Github issue with a brief description is required.

Topics that may introduce complicated code changes, significant user experience changes, should be prepared with a well-documented presentation to describe the purpose, impact to user experience, impact to the code base, impact to extenders and scope of the work. Please expect these topics to be discussed in several meetings. This will give people enough time to understand the suggestion, share thoughts, raise concerns and questions. A Github epic is required to break down the work into phases.

Join the discussion

• We will try our best to cover all topics, but please be patient if your topic can not be scheduled in the running meeting.
• On-paper documentation or presentation is strongly recommended to track discussion. It's required for complicated topics.
• Necessary investigation and research homework related to your topics are recommended. This helps us to stand on the same page during discussion.
• Be prepared that your idea(s) could be challenged.
• Keep open-minded on new idea(s) from other people.
• Focus on the topic itself, avoid making unnecessary comments not related to the topic.
• Follow the code of conduct and remain civil conversation.
• If a topic of yours is being discussed and a debate begins, please be aware of the time as there may be others on the agenda lower down who are waiting for your topic to end.
• When a topic is being discussed please do not interrupt and also when talking please leave time for others to be given a chance to speak and be willing to take topics off-line for further discussions in issues tracking or specific meetings. A good practice is to put yourself on mute when you are finished and to take yourself off mute to "raise your hand" so that the meeting chair can call you in to put forward your viewpoint.
• The most important thing is to be civil. When an idea is being challenged do not challenge the individual who came up with the idea, and when your idea is being questioned please listen to other viewpoints and be respectful of everyone's opinion and viewpoint.