Sprint Planning Meeting: Wednesday, December 8th

[github-actions]

2i2c Sprint Planning meeting

This is a 60 minute recurring meeting every other Wednesday at 7:30AM Pacific time (here's a timezone converter, ignore the date!).

Our goal is to synchronize the team on the most important things to work on, and to divide work between one another so we know what to work on next.

• Sprint Board
• Deliverables backlog

Meeting roles

• Meeting facilitator:

Meeting agenda

Follow the agenda below, checking boxes as we complete each step.

Review the Sprint Board. (10m)

• Celebrate our accomplishments
• Archive deliverables we finished

Populate Sprint Board with new deliverables (45m)

• Review in-progress deliverables from the last sprint: drop or carry over items as needed
• Review a few more urgent items in the deliverables backlog
• Add new deliverables to Sprint Board
• Somebody is assigned to each deliverable
• Everybody agrees the current cycle's plan is realistic and that the right items are on the board.

Support steward (5m)

• Support steward describes any open support issues.
• Support steward transition issue is opened

[choldgraf]

Hey all - after our meeting discussion this morning, I've taken a pass at the Team Backlog board and tried to shrink it down quite a lot. I suspect that our first planning meeting will be a little bit bumpy as a result, so in our meeting lets try to to the best we can with it :-)

Quick update on the new process we'll try to follow:

• No longer trying to refine deliverables down to "bite sized" items.
• Instead, our development efforts will be focused around "projects". These have a fixed time, a rough solution idea, and you are encouraged to evolve the "tasks / deliverables / etc" as you work on it.
• Projects will have a champion and assistant assigned to them.
• We'll also need to divide up our "operational tasks" amongst the team

So I think this meeting will be something like:

• Figure out who is in the middle of projects that they need to keep going, and we should agree on the appetite we'd like to give it moving forward.
• For people that have the bandwidth to pick up a project, let's choose from the short list in the team backlog
• Add assistants to the projects that are in-progress
• That backlog still needs some work, so we may need to do more discussion than normal tomorrow.
  • Before this meeting I invite anybody to shape up the items that are there so there's more context for others, or to add one or two new items that you think are really important.
  • In the future, I'll try to host regular weekly project brainstorming and shaping meetings so we can iterate on these in a more reliable fashion.

As we are getting close to holiday times, I suspect we don't want to embark on anything super complex. That said, just to context share a bit, looking at the sprint board now here's what I see:

• @consideRatio isn't championing a major project, but I am not sure if ones that are on there are within scope for the JMTE grant. Perhaps @consideRatio would be willing to brainstorm a project idea with me after our sprint meeting?
• @damianavila doesn't have a project on our sprint board, but he and I should come up with a project focused on the PyData theme, perhaps we can discuss this after the meeting.
• @GeorgianaElena has her hands full already, as she is basically spearheading two projects simultaneously! Perhaps we should hand off one of them to another team member so that she is not doing two things at once.
  • Migrate UToronto hub to our pilot-hubs repository infrastructure#638
  • Enable authentication via CILogon infrastructure#315
• @sgibson91 isn't championing a major project, though is focusing on AGU stuff right now. I believe that @sgibson91 expressed interest in working on our CI/CD infrastructure (project at CI/CD infrastructure for hubs that is automated, tested, and parallelized  infrastructure#879).
• @yuvipanda isn't championing a major project, but maybe he should be dedicating more of his time to project shaping / guiding others, etc. We should brainstorm in the meeting!

We also have an event that OpenScapes is running with AGU starting next weekend.

[sgibson91]

• @sgibson91 isn't championing a major project, though is focusing on AGU stuff right now. I believe that @sgibson91 expressed interest in working on our CI/CD infrastructure (project at CI/CD infrastructure for hubs that is automated, tested, and parallelized infrastructure#879).

Correct, with some caveats. I'm also working on CarbonPlan Azure-based stuff and that's a single point of failure as I'm currently the only one with access to the subscription. I will also open up another project about migrating Pangeo's Binder and I think we'll have some prioritisation to do against the CI/CD stuff and that.

[choldgraf]

closing this one - I believe that @GeorgianaElena and @yuvipanda still need to do a support steward sync (#327) but that happens outside of this team meeting!