Productive Scrum Teams
Be Like a Rafting Team
25 September 2013
Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.
We have been using Scrum for about two years and have mostly good experiences -- apart from few bitter ones, when user stories were pouring in between sprints.
Scrum is like a rafting team; if anybody gets tired, then we may lose control of raft. Every team member matters and is equally important in the Scrum team, so we have to balance the workload if we find that, for example, the Dev/QA folks are overworked. Other team members can do whatever they can to help. The good part is that this actually happens in Scrum teams; volunteers come forward in daily meetings and take on some tasks.
The worst thing about Scrum is that it is more prone to new stories being introduced between sprints, which hampers producing quality output.
My suggestion to fellow Scrum soldiers: The best method for Dev/QA is to do some hands-on analysis before the stand-up. If necessary, have a chat with stakeholders for a couple of minutes; this way you can use the stand-up call only for quality blockers, and everyone will have time to tell their stories within the 15-minute time frame.
Current rating: 4 (3 ratings)
The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.