Changes to Iteration Lengths for Projects #2
Vetpetmon
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Internal announcements: This is just a notice that we are changing iteration lengths from 1 week to 3 weeks at a time for our projects.
For those outside of VPML, I am just notifying you that we're having to change things around behind the scenes! The changes should only positively affect our software from now on.
Why were iterations short before
Iterations spanned across 1 week to account for 1-2 members working on a project. This made it easy for those 1 to 2 people to know what to do next and when, while still keeping workloads manageable. This system was good when there were only 3 members in the VPML team. Ever since we hit 7 members (1 member has not made a GitHub account at all yet!) productivity has been thrown awry as we figure out how to re-organize the team into operations that can be up-scaled without causing serious rubber-necking.
What 3 weeks means for everyone
3 weeks allows for larger groups of assignees to collaborate effectively on a task without putting too much time pressure or constraints. Rushing doesn't help with releasing updates sooner, nor does it encourage striving for quality and stability. With a larger member base, more time to communicate means everything.
Beta Was this translation helpful? Give feedback.
All reactions