Work organization and kanban boards #71
petrovicboban
started this conversation in
Ideas
Replies: 1 comment 1 reply
-
Agree, I like the separate Kanban boards we've started. Also do think we could attach more semantic meaning to our release versions. One hesitation is we're still a light team and I don't want to go overboard on process. We'll be closing out our first milestone (initial Python release) shortly so open to trying this as we prioritize the next milestone. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Since it became obvious we can't use single board for the whole life time of the Rforestry development project (unless we continuously delete finished tasks, which is not good idea), we need to come with and ideas of how to approach this.
One possibility is to have board per milestone, and milestones could be every new MAJOR.MINOR version. Every board would start with a bunch of TODO tasks, and once all of them are in Done state, we could release that version. This would resemble traditional sprints, except milestone would not be limited with standard 2 weeks interval, it might take more for next MINOR version.
Tasks can be added in TODO in the middle of work between two MINOR versions, not just on the beginning of it. But, it the amount of time to finish it is significant, then developers can decide to set that task for next milestone.
In case where we need urgent security patch / bug fix, we can have patch release, before main milestone release.
Any ideas? @edwardwliu @theo-s
Beta Was this translation helpful? Give feedback.
All reactions