This document discusses engineering practices within Scrum and proposes updates to the Agile Manifesto. It begins by summarizing the four values of the original Agile Manifesto. It then argues the Agile Manifesto is outdated and proposes expanding on its values. The document outlines goals for improving the current state of Agile, including demanding technical excellence, promoting culture change, maximizing business value, and organizing knowledge. Finally, it lists six engineering practices within Scrum: requirements elaboration management, configuration management, integration, layered testing, agile architecture and design, and coding standards.

1. Engineering Practices within ScrumBy Mike BeedleEnterprise Scrum Inc.

2. Manifesto for Agile Software DevelopmentWe are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactionsover processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.Agile Manifesto

3. Agile Manifesto+Agile is outdated, and it is not what experts do today. Even as defined it is poorly implemented: Individuals and interactions over processes and toolsWorking software over comprehensive documentationCustomer collaboration over contract negotiationResponding to change over following a planI prefer to say the state of Agile is now (in the best scenario):Beyond Individuals and interactions to hyperproductive Swarming jelled teams and communities of practice

4. Beyond working software to well architected and well-tested user-centered software services

5. Beyond customer collaboration to user collaboration and user involvement