Unfortunately, I went on vacation the last day of the iteration, missing the demo and retrospective. From my perspective we stubbed our toes a bit.
We focused on our most recent app that had been developed using BDD. It was the teams first shot at it, so there were definitely rough edges to our practice of it.
We're struggling a little with defining what our tester should be doing. Our current focus is helping with developing acceptance tests and doing some exploratory testing. This felt awkward during the first week because our tester didn't have access to our git repository and was sick/working from home at the beginning of the sprint. So we didn't communicate or share the acceptance tests we had already developed. I hope getting access to the git repo will help some of this. Regardless, we need to take time to discuss them.
Another painful spot was a story that ended up bring much larger than expected. What made this painful was we recognized that there was more work and discussed it as developers, but neglected to create a task to expose it. So when we ran into some trouble we ended up splitting the story at the last minute.
Finally, we had some difficulties working through the automation of our acceptance tests. Between learning how to write the tests and learning the tools (cucumber and geb) we stumbled a couple times.
While I enjoyed Florida, I was a little sad to not be with the team as they start the second week of this.
We focused on our most recent app that had been developed using BDD. It was the teams first shot at it, so there were definitely rough edges to our practice of it.
We're struggling a little with defining what our tester should be doing. Our current focus is helping with developing acceptance tests and doing some exploratory testing. This felt awkward during the first week because our tester didn't have access to our git repository and was sick/working from home at the beginning of the sprint. So we didn't communicate or share the acceptance tests we had already developed. I hope getting access to the git repo will help some of this. Regardless, we need to take time to discuss them.
Another painful spot was a story that ended up bring much larger than expected. What made this painful was we recognized that there was more work and discussed it as developers, but neglected to create a task to expose it. So when we ran into some trouble we ended up splitting the story at the last minute.
Finally, we had some difficulties working through the automation of our acceptance tests. Between learning how to write the tests and learning the tools (cucumber and geb) we stumbled a couple times.
While I enjoyed Florida, I was a little sad to not be with the team as they start the second week of this.
No comments:
Post a Comment