Systems Squad Issue Tracking and Scrum

In order to establish successful, efficient discussion on technical questions and issues, please check below guidelines.

Issue tracking

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

System Squad Scrum Meeting

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

Meeting agenda

Please be aware that the scrum meeting may already have agenda. Usually the agenda is mostly aligned and prioritized to current PI deliverables.

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

Agenda priority

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

• Topics may have big impacts:
  • before LTS, topics which may introduce or potentially introduce breaking changes,
  • align to major deliverable planned in current PI,
  • critical failures, blocking issues either identified by Zowe teams or customers.
• Topics raised by Europe timezone, since it's late for Europe colleagues.
• Non-blocking failures.
• Nice-to-have improvement ideas.
• OK-to-have improvement ideas.
• After LTS, topics which may introduce or potentially introduce breaking changes have lower priority since it means can only be introduced in next LTS.

Please be patient if your topic cannot be scheduled to be discussed. We will try out best.

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 brief description is required.

Topics may introducing complicated code changes, significant user experience changes, should be prepared with detail documented presentation to describe the purpose, impact to user experience, impact to code base, impact to extenders. These topics should be expected to be discussed in several meetings to give people enough time to understand the suggestion, share thoughts, raise concerns and questions.

Join the discussion

• We will try our best to cover all questions, but please be patient if your topic can not be scheduled.
• Necessary investigation and research homeworks are recommended. This helps us to stand on same page on discussion.
• Please remain civil.