The Jira/Confluence backlog has been moved to YIS - JIRA-APPS Scrum Board If you have any questions regarding improvements on the backlog or a new improvement request, please contact a Jira administrator or join the Jira Community Chapter.
Jira Chapter
The Jira Chapter meetings are canceled, due to overlap with other meetings where Jira/Confluence is also discussed as a topic, such as Scrum Chapter.
The following proposal has been agreed on 1-2-2023 with attendees in the Jira Chapter meeting:
A workshop will be arranged once every 2 to 3 months in which a clear agenda with topics is presented. Anyone from Information Systems Division can join when interested and request topics (questions/improvements/adjustments) by the Jira administrator to be added to the workshop agenda.
Jira changes will be updated in the manuals, if there is any unclarity, reference can be made to the training material. If not found ask Jira administrator to explain.
Suggestions for improvement/adjustments can be discussed within the teams. The scrum masters can ask the Jira administrator to add a PBI (product backlog item) in the Jira Board.
The Jira administrator will join the Scrum Master chapter on regular basis and can be invited when Jira/Confluence topics are on the agenda of any other meeting as well.
Communication
Updates can be send in a newletter via e-mail with the higlights of updates and Jira fields changes including a reference to the training material.
Include Jira/Confluence as topic in the Townhall meeting.
Planned maintenance will be informed via banner in Jira and the customer portal(s) and in the Jira Maintenance Teams group.
Jira/Confluence information regarding unexpected situations is sent by email and, if possible, communicated via banner in Jira/Confluence and the Jira customer portal(s).
How can I bring my brilliant improvement idea for Jira/Confluence or Bitbucket to the Jira team? Reach out to a Jira admin via MS Teams or e-mail, for Bitbucket please reach out to Marcel Smit.
How can I ask support for Jira, Confluence or Bitbucket? Please raise a ticket for Infra Servicedesk via the Jira Customer Portal
Add all IT projects, used Issue types but Programme and Project
...
SD link screens to new Team Yamaha field (double maintenance for YIS issues) Bianca van der Meer Image Removed
YPM - transition move to development board screen etc. Team select screen Bianca van der Meer
...
Bulk updates per team to fill Yamaha team field, same as Team Yamaha. If there are more then 2 removed from selection.
Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty. Fill Yamaha team field if we know team.
Selection of issues where Team Yamaha contains more than 1 team and Yamaha team is empty, inform team leads to set Yamaha team field.
Yamaha Team
B2B-ANALYSTS2639 Bianca van der Meerissuetype not in (Programme, Project) and "Yamaha Team" is empty and "Team Yamaha" = "team#B2B-ANALYSTS" and assignee is empty, 3 left to which team to be assigned René van der Pal
Where should we create epics? YPM or YIS? (Arthur, Benjamin) Bjorn says there is no standard. B2B uses YPM, B2C uses B2C. And no owner who can decide on this. AJ van Spanje [AgileVisor]
Can we have a Yamaha-Team for PO's per product, to priorities/prepare work? (Arthur le Blanc, Benjamin Smits, Stefano Arzuffi, Marc de Graaf) Salesforce-POs Bianca van der Meer / AJ van Spanje [AgileVisor]
EPIC used for operational support, deployments, user authorization, Jira activities, J-sox, gdpr, sql approval, job change request, replace by SD classification list = Bianca van der Meer / AJ van Spanje [AgileVisor]
Location of acceptance criteria → impossible. Let's deactivate acceptance criteria for this reason, and use Description instead. AJ van Spanje [AgileVisor]