The document discusses using lean principles to improve enterprise agility in software development. It defines waste as anything that does not add value from the customer's perspective in either products or processes. Eight common types of waste in software development are identified, including partially completed work and defects. The document proposes a lean lens game to help development teams identify waste in their processes by acting out scenarios and mapping out value streams and waste. Practical takeaways include using value stream mapping and discussing waste regularly in retrospectives to continuously improve.