runtimeverification / kontrol

BSD 3-Clause "New" or "Revised" License
51 stars 6 forks source link

Kontrol Weekly Update #83

Open yale-vinson opened 1 year ago

yale-vinson commented 1 year ago

Weekly report to update progress made by the Kontrol Team, comprised of a bullet list of where we are, what was completed, what's up next, etc., as well as a blog style recap for those that might want a little more detail.

As usual, the author reserves the right to modify the format as the project progresses in order to strive for continuous improvement and utility for the audience.

yale-vinson commented 1 year ago

TL;DR Summary

Where We Are

Up Next

The Week That Was (29 Sep - 5 Oct)

I will try to normalize this over the next few weeks, but for this week I want to focus on some general items that the team has been working on over the last several weeks to reorganize the work on Kontrol.

The Triage status was a bit of a dumping ground with several aged items, so the team spent a few Standup meetings moving these items to the Backlog, In Progress, etc. to empty the Triage list except for items added since the last Standup.

Next, we added a new section to the Project Board inspired by the K Team titled Next Up, which is a list of the highest priority items from the Backlog. When the team completes an item or finds themself with bandwidth, they will first look at Next Up to ensure that we are focused on the most important items.

We added a few other nuances to the project board, listed below:

Once we reworked these elements, Palina and I worked on re-prioritizing the Backlog and reviewed the Backlog with the team to ensure that we got the order right. From here, we are using the following general criteria to assess the relative priority of new issues opened in Kontrol:

It is important to note that, much like the Pirate Code, these are guidelines as opposed to hard and fast rules, meaning that each item can be considered higher or lower priority depending on a number of factors that are not addressed in the criteria above.

With this new framework in place, the team meets Tuesday and Thursday to work through the Triage list to avoid a buildup, then update status on Issues In Progress, and assign new tasks to team members with bandwidth. In weeks to come I will update this Issue in the Maintenance section of the Project Board with details on how the work is progressing, so look back here every Friday for the latest news on Kontrol.