revise admiral core mtgs

[duniek]

Background info:

As we bring on more contributors and start moving into more of a maintenance phase for the admiral core package, it is time to adjust our meeting structure. From now on the focus for the core team will be to bring and support contributors, as well as review and accept their work. It is suggested to shift even more towards Kanban with continuous planning and progress, rather than sprints.

Definition of Done:

Team agreement and potentially new way of working implemented.

[duniek]

@pharmaverse/admiral
During our Sprint Review/Planning meeting (02MAR2022) we agreed to shift the way we operate as a core admiral package team.

Key points: 1) Start working continuously in a Kanban fashion (that's why we renamed the columns in our project board). This means that:

• We pick issues from the column and put them as we start working on them. Then when we finish, we start a new task.
• No more Sprints and Sprint plans.

2) Keep stand-ups twice a week and stick to 15 minutes

3) Have retrospectives ad-hoc but at least monthly

4) Core admiral package team focus is on:

• delivering ADLB functions
• getting tester feedback implemented (ideally getting the contributors to work on it)
• reviewing pull requests
• fixing bugs
• improving the documentation
• onboarding and supporting contributors
• onboarding core developers
• coordinating across admiral packages

5) Besides the stand-ups, the following meetings will continue/start:

• weekly Q&A discussion meetings (whole admiral core team)
• bi-weekly admiral core backlog grooming meetings (for now Ben, Thomas, Robin, Ojesh, Kamila?)
• monthly? cross-package alignment meetings (Leads from all admiral packages)

Background: Until now we used the Scrum framework as a guidance, which was providing us with a structure to prioritize, align on the plan and stay in touch with each other. As the key focus for the team shifts to PR review and maintenance it makes sense to adapt the way we work. We will meet and assess how that works for us in a retrospective.

[bms63]

Nice summary!!

I think you are right Kamila for us to have the Further Priority Issues and Top Priority Issues collapsed into one Column

So

Proposal for Board Naming Convetion:

ADaM Backlog > Priority Issues > In Progress > In Review > Done > Archive

Could we change name of project from admiral scrum board to admiral project board or something that reflects the new kanban framework?

[duniek]

Thanks Ben. I adjusted the name of the project board and of the column names. If no one else comes with another proposal this will be it for the time being. I also merged the priority columns.

I think our board looks simple and neat now. We can probably reduce Done and Archive into one column as well, but that's not so important. BTW is there a way to 'move' issues from Done to Archive in bulk?