Both of our applications that use the Scrum development framework have now halved their iteration cycles from 4 weeks to 2 weeks.
2 Week Sprints!
This felt rather daunting at first. I was worried that there just wouldn’t be enough time to actually develop something of billable, business value for our customers. However, I have been pleasantly surprised by the universal acceptance of this change. Developers, analysts and managers all report to less confusion about the relevant content of the Product Backlog – this has many cross-overs with some Getting Things Done principles regarding removing clutter.
With this one simple process change we now feel much more ‘sprinty’: able to really focus on a smaller number of work items. We have also doubled the amount of feedback measured and adaption possible; velocity is also more meaningful.
So, highly recommended. I wonder if we’ll move to a one week sprint as Ken Schwaber currently recommends? Xtreme sprinting!