When it all comes together
ByWe all know the different phases of team development: forming, storming, norming and performing. In this last sprint I saw the team go from norming to performing.
In my 6 years of Agile practice this last sprint was as close as I seen a team do all of the best practices of a Scrum team.
It started with an excellent planning session at the beginning of the sprint. We actually took 3 hours to do our sprint planning. The product owner did an excellent job of clarifying the requirements and the team came up with a very comprehensive set of tasks for the sprint. Our testing engineers participated and helped us understand the issues we would face in testing our code.
The sprint started on a Wednesday and by the next Monday we were completing the first of the user stories and QA was doing their final testing. The user experience designer (UED) was constantly updating the high fidelity wireframes to reflect the necessary changes in the user interface. We had a hour of the product owner’s time each day to clarify ambiguities in the requirements. Through the rest of the sprint we were finishing new user stories and they were accepted by QA, UED and the product owner.
Our velocity actually increased during this sprint. We brought forward two user stories from the next iteration into the current iteration.
Team members stated that the last days of the sprint did not seem like a mad rush to finish the user stories. We only had two user stories out of 16 that needed to be finalized and tested in the last two days of the sprint.
The sprint demo was flawless. It was the climax the hard work and excellent team work of a performing team.