Oscillation versus Iteration

This content is syndicated from Jim Highsmith .com by Jim Highsmith. To view the original post in full, click here.

Short iterations can cause Agile teams to lose focus and begin oscillating rather than iterating. This can happen from several perspectives—business, technical, user—and it’s something that Agile teams need to be aware of and guard against. When customers change their minds on an user interface issue over and over again—oscillation may be the issue. When developers skip from one design to another over and over—oscillation may be the issue. When product owners churn stories into and out of an iteration—oscillation may be the issue.

Iterations converge on a completed story, feature, or objective. Oscillations send us back and forth between states with little forward progress. It’s difficult at times to tell the difference, but when an oscillating situation seems to be happening, someone needs to stand back and say, “stop.” This is the time to stop and re-evaluate the situation. Two typical problems are: 1) the participants don’t understand the problem, or 2) the participants have different opinions about the solution. In either case, continuing on won’t resolve the issue.

Often the problems arise from not having a well-defined context for the work, for example, not having a good theme for an iteration or release. When discussions about a particular story (how much functionality it should deliver for example) seem endless, then maybe it’s because the team doesn’t have an anchor point in terms of what they were trying to accomplish during the iteration. When two developers are endlessly arguing about a design approach, maybe it’s because the team failed to set basic design guidelines.

Teams without release plans often oscillate in iteration planning because they lack the overall theme and context of such a plan provides. I once worked with a cell-phone software team during a particularly volatile time in the industry. Standards were changing and manufacturers were changing their requirements frequently. The team felt that they were going in circles—and their solution was to freeze requirements. Unfortunately, that would have been disastrous in the market. This was a case in which changes, while seemingly oscillations, were just normal for the industry at that time. The company did need to adapt to these changes and iterate towards a solution. By going back to the business objectives for the project, in this case the multitude of changes were justifiable.

So separating oscillation from iteration isn’t always easy, but it’s a skill that good Scrum Masters, project managers, iterations managers and teams need to cultivate.

Leave a Reply

What is 1 + 5 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”


“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”


“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”


“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”


“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”


“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”


“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”


“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”


“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”


“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”


“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”