One Week Iterations

Process

Description

Working in an iterative fashion is a cornerstone of Agile development processes. The timeframe for an iteration varies depending on many factors, including the particular methodology selected. Extreme programming (XP) teams may choose 1-2 week time-boxes as their iteration units, while 1 month "sprints" are specified in Scrum.

One week iterations are probably the smallest effective time-box and more "extreme" choices that can be made by an (XP) team. Performed effectively, one week iterations produce tighter feedback loops and help keep story scope small and manageable.

Many teams that choose one week iterations do so religiously.

Firms practicing One Week Iterations

  • Hashrocket

    Hashrocket has always used one-week iterations. It's a bit easier for us to do so than other shops, since we let Pivotal Tracker handle iteration planning for us instead of having a weekly iteration planning meeting (IPM).
    7

  • eLabs

    4

  • 8thlight

    4

  • VinSol

    We follow one week iterations. The iteration ends with a weekly meeting. I shall post a link to the checklist of our weekly meeting soon.
    3

  • Microplace

    Not only our iterations are one week long, we also go live every week. At least for the most part. Once in a while we can't break something into small enough chunks and can only go live after 2 weeks. But even then, we make sure we provide measurable value every week.
    2

  • Bakedweb

    2

  • Pivotal Labs

    2

  • Integrum

    We plan all of our client work into week long iterations, with a locked iteration after the planning session. No new user stories are added after the weekly iteration is planned. Lather, rinse, repeat.
    2

  • Eden Development

    1

  • Asynchrony Solutions

    1

  • OpenHallway

    1

  • Cloudspace

    1

Sponsored By