Ken Orr wrote ( in Cutter IT Journal Vol.3, No. 7 ):

Agile . since Jun 23 . Index . DOCs TOP TOC

Continuous Integration


Because of its emphasis on speed, agile development focuses on constant integration. Rather than have a set of periodic program (system) builds, the code base is in a state of continuous integration. New programs can be added at any time. The pair programming teams integrates the code base. If something fails, typically the team that has made the most recent changes is normally the group that tracks down the problems. From work in TQM and lean manufacturing, it is well known that the shorter the cycle between manufacturing and testing, the better the ultimate end product.

Agile . since Jun 23 . Index . DOCs TOP TOC

The 40-Hour Week


Agile development gurus preach that software development is more like a marathon than a sprint. In knowledge-based work, it is important that the individuals that make up the team be as fresh as possible. Although there is not much that software development managers can do to help team members avoid stress and burnout at home, they can certainly do so on the job.

The rule, then, on agile development projects, is that people in the normal development cycle only work 40 hours a week. Though there may be occasions for overtime, there shouldn't be overtime worked more than one week at a time: in other words --no death march projects.

Agile . Index . DOCs . TOC