Discord Server

[retailcoder]

Join link (no expiry)

With Rubberduck3 going to a 2-week sprint development schedule, we need to rethink our collaborative efforts - ad-hoc contributions won't work in the context of a multi-process re-implementation of pretty much every single part of Rubberduck, we need a solid, structured plan with clear priorities.

We know what needs to be done, at least the large blurry outlines: these blurry outlines paint a high-level view of the 3.0 release milestone, and I will lead the charge wearing the PO's hat ("product owner", in Agile terms) to break down the large blurry blocks into smaller, focused issues with enough documentation that exactly what needs to be done and why, is crystal-clear for every prioritized issue that gets into a sprint, so technically anyone could pick up any task at any point in time.

After each sprint, I want to take a moment to go over what was achieved and discuss the code and approaches taken, assess where we stand versus the backlog, whether we have a healthy backlog or if I'm falling behind with the documenting, etc.; this assessment will happen every second Saturday (given 2-week sprints) at 9 AM (EST) with or without an audience, but if we start building an audience it could be nice to present/demo the features we've delivered in the sprint. If it's just me in the dedicated Discord voice/video chat then I'll just drop a bunch of screenshots and a summary of the sprint activity.

At the beginning of each sprint (so, around 10 AM (EST) every second Saturday, i.e. immediately after the sprint review), we shall be planning the work for the upcoming two weeks, taking into account the size of the stories/issues as well as how many hands are expected to be on deck at any point during these two weeks. Once a realistic workload is established, the sprint kicks off and we pick a ticket to work on, and move forward following the established priorities.

If we run out of work for a sprint for whatever reason, we can pull tickets we had pished to the following sprint. Sprint objectives are completely fluid, until the sprint begins.

If we fail to deliver a sprint's objectives, we adjust the following sprint accordingly, and no biggie.

I think Discord will be a good tool to support this. Will you hop aboard?