What are deliverables in agile and why do we have them?

Agile methodology, rooted in the Agile Manifesto written over 20 years ago, often sparks strong emotional reactions, particularly around the concept of documentation or deliverables. Deliverables, which are outputs produced during a project, can be internal or external and tangible or intangible, and they serve two primary purposes: communicating product design aspects and providing proof for governance, especially in regulated environments. Although agile prioritizes working software over comprehensive documentation, deliverables remain essential for clarity and accountability, ensuring that all stakeholders are aligned and that decisions, particularly those made long ago, are well-documented for future reference. The key is to understand the value of each deliverable by asking why it is necessary, which helps maintain the focus on developing effective products while adhering to agile principles.