Open Stack

Elizabeth K. Joseph wrote:
> [...]
> We found these virtual sprints to be incredibly valuable for knocking
> out work items that we'd defined at the Summit and in Specs. By
> focusing on specific work items we were able to spend just a day or
> two on each sprint and we didn't have the travel time (and jet lag!)
> penalty that physical sprints have. They were also relatively easy to
> schedule around the particularly active travel schedule that our team
> members have.
> [...]

That's great feedback, thanks Liz!

Personally I think F2F sprints are great to make a team converge to
common objectives, by sharing as much understanding as possible using
high-bandwidth discussions, but also spending time together off-work.
For example, the original storyboard sprint in Brussels last year was
great to build a common understanding of the goal and get all the team
behind it. I don't think a virtual sprint could have achieved that.

But if the convergence and common understanding of the goal is already
there, then virtual sprints are nearly as good to get work done, much
easier to organize, and more inclusive. Once that shared understanding
is built, it's also totally doable for smaller teams to maintain it by
leveraging design summits F2F discussions only, without the need for a
F2F midcycle sprint.

> Some lessons learned:
> 
>  * Schedule as far in advance as you can, taking into account the core
> people needed to complete the task
> 
>  * Block out time for the sprint in your schedule
> 
>  Just like being at a physical sprint, ignore much of the rest of IRC,
> mailing lists and other meetings and be present at the virtual sprint.
> Continous presence in channel helps the team tackle problems and
> coordinate work.

That's what I struggle to do. F2F sprints force me to focus. In virtual
sprints, I have to force myself to focus... but I agree it's critical to
the success of the virtual sprint.

> [...]
>  * Use a common Gerrit topic for the sprint
> 
> In order to help others in the sprint review changes, use a common
> topic in Gerrit for all changes made during the sprint, this can be
> set upon submission to Gerrit with: git review -t sprint-topic-here,
> or afterwords by the owner in the Gerrit UI.

++

Regards,

-- 
Thierry Carrez (ttx)