Semester 2 Week 3 (1/31-2/6)
This week we shook our working practices out and revised them when they didn't work. Will and I took on our new responsibilities while the team adjusted to a revised sprint schedule. This week culminated in a pretty disastrous QA session which while extremely problematic exposed several issues with how we had been proceeding that can now be addressed.
Will took over as the Scrumlord and he set about revising our scrum habits and sprint schedule with a lot of energy. It was really refreshing to have a confident and steady hand at the tiller though I really don't like Sunday work meetings. I think Will has done a really good job getting everyone to report what they've done each day at scrum and he's worked to make scrum more relevant to how we work. I've had an eventful first week as the QA Liaison for my team, after going over the documentation early in the week I discovered on Thursday we did not have a stable build (despite that having been a specific work goal the day before). Despite the team's best efforts we did not have a stable build before QA on Thursday. However since then we have taken the lessons we learned and refined our build policy so that we will reliably have a stable build in time for QA.
I think it would be helpful to have a critique of the story and feel of the game. Right now it sometimes feels like the team is so completely sold on the story that none of us are questioning it when it needs to be questioned.
No comments:
Post a Comment