Skip to main content

What is an Iteration?

Cote included among his recent del.icio.us links an article by Alistair Cockburn on iterative development.

The crux of the issue Cockburn raises is that "[d]anger grows when the results of [an] iteration are not directly linked to delivering the product to the end user."

To realize the benefits of iterative development, your iteration cannot simply be a development time period that culminates in testing and refinement of the plan for continuing development of the product. An iteration must result in a working release of the product to an end user. I have made this point in the past:
"With iterations, you perform the steps to yield a working version of the product for review."
That is, the tests you run shouldn't just determine whether isolated features or pieces of the product work, but whether the end-to-end processes users perform are working.

Why is it so important for iterations to yield a working, releasable product? One reason I've mentioned:
"Implementing the product and demonstrating it to prospective customers almost always results in the discovery of new requirements or the recognition of errors in the original requirements."
Another reason is that it prevents product developers from getting side-tracked. A developer might, for example, get bogged down implementing a particular feature. What's important, however, is not the feature itself, but what requirement it was intended to satisfy. If the developer is focused on satisfying the requirement instead of implementing the feature, she may (acting with "agility") simply choose to ditch the feature and satisfy the requirement by different means.

Comments

Popular posts from this blog

Why Spreadsheets Suck for Prioritizing

The Goal As a company executive, you want confidence that your product team (which includes all the people, from all departments, responsible for product success) has a sound basis for deciding which items are on the product roadmap. You also want confidence the team is prioritizing the items in a smart way. What Should We Prioritize? The items the team prioritizes could be features, user stories, epics, market problems, themes, or experiments. Melissa Perri  makes an excellent case for a " problem roadmap ", and, in general, I recommend focusing on the latter types of items. However, the topic of what types of items you should prioritize - and in what situations - is interesting and important but beyond the scope of this blog entry. A Sad but Familiar Story If there is significant controversy about priorities, then almost inevitably, a product manager or other member of the team decides to put together The Spreadsheet. I've done it. Some of the mos

Interaction Design: the Neglected Skill

Your product development organization has a big, gaping hole in it. (Be prepared to feel defensive as you continue reading.) One of the most important roles in product development is the role of interaction designer. An interaction designer designs how the users will interact with the product and conceptualize the tasks they perform. He decides whether, for example, the user interface will be command driven, object oriented (clicking on objects then specifying what to do with them), or wizard based. The interaction designer decides the individual steps in the use cases. Every company has one or more people that play the interaction designer role. Usually, those people have little or no expertise in interaction design. Sadly, they typically don't even realize how unqualified they are. Let's see who typically plays the role at companies. Engineer . An engineer is an expert on building what is designed. Yes, an engineer may know how to design the internal structure of the hardware

Is Customer Development Pseudoscience?

The “Science” of Lean Startup Lean startup practitioners embrace the scientific method, seeking the "truth" about what business model and strategy will lead to product success. We do so by: Formulating hypotheses Crafting and running experiments to test them Learning from the experiments Iteratively feeding our learnings back into revised hypotheses Sounds pretty scientific, at least in spirit, doesn't it? Yet this process actually neglects a key ingredient in the scientists' mode of operation. To identify what’s missing, let’s examine “customer development”. Customer Development Steve Blank is one of the pioneers of the lean startup movement. He introduced into the lean startup lexicon the term “customer development”. Customer development consists of sessions and interactions with customers to test hypotheses. For example, a product manager might interview a prospect, asking if she agrees with the product manager’s hypotheses about the problem