The document argues against using projects to organize software development work. It claims that projects assume perfect knowledge and flexibility that do not exist in software. Projects optimize for big batches of work but software has diseconomies of scale. It is better to organize around stable teams working continuously in small batches to reduce risk and destroy knowledge less frequently. Teams should be organized by business streams rather than projects to focus on continuous benefit delivery.