And at the same time we have to try to improve the economic performance of software development enough so that someone will listen. In the next chapter, we will see how such ridiculously simple solutions could possibly work. Where a practice is weak, the strengths of other practices will cover for the weakness. Later chapters will cover some of the topics in more detail. As reality overtakes the plan, update the plan.
Extra complexity is removed as soon as it is discovered.
Customers write tests demonstrating that features are finished. Never work overtime a second week in a row. Include a real, live user on the team, available full-time to answer questions. In this chapter we will quickly summarize what is involved in executing each practice. The Planning Game Neither business considerations nor technical considerations should be paramount.