Join the Agile Community

With more than 4261 members located around the globe, the Agile Alliance is driven by the values and principles of the Manifesto for Agile Software Development

We support those who explore and apply Agile principles and practices to make the software industry productive, humane, and sustainable.

Knowledge Repository

Search for text or agile alliance members

Applying Queueing Theory to Sprints

by Juan Banda (2009-09-24) permalink

Read the full article

I realized time ago that the Quality Engineers (QEs) in my projects were doing not much during the beginning and first half of the Sprints and this was like a recurrent pattern; they created test cases, prepared tested environments, updated existing ones, did some research, write training documents, etc. That sounds kind of ok but the problem was that by the end of the iteration they were all of a sudden overwhelmed by the amount of user stories that they had to test. Consequently, they had to work killing hours (including weekends) to get the work done.

I remembered that time ago banks had a similar problem, tellers where not doing much during most of the day, but at peak hours they can hardly breathe because they have a bunch of impatient clients formed on a lane in from of them. Banks played smart and did something to improve their service systems; they did something to evenly distribute arrivals. Queuing theory-wise, if you can’t increment servers, go in the other direction and look for an stable arrival rate.

Rating: 5.0 out of 5 (1 rating)
Source: Juan Banda's blog page
File Type: HTML
Owner: jbanda
Categories: Lean Development
Updated: September 30, 2009


Comments