Engineering Practices within Scrum<br />By Mike Beedle<br />Enterprise Scrum Inc.<br />
Manifesto for Agile Software Development<br />We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: <br />Individuals and interactionsover processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan <br />That is, while there is value in the items on the right, we value the items on the left more.<br />Agile Manifesto<br />
Agile Manifesto+<br />Agile is outdated, and it is not what experts do today. Even as defined it is poorly implemented: <br />Individuals and interactions over processes and tools<br />Working software over comprehensive documentation<br />Customer collaboration over contract negotiation<br />Responding to change over following a plan<br />I prefer to say the state of Agile is now (in the best scenario):<br /><ul><li>Beyond Individuals and interactions to hyperproductive Swarming jelled teams and communities of practice
Beyond working software to well architected and well-tested user-centered software services
Beyond customer collaboration to user collaboration and user involvement
Beyond responding to change to prioritizing and optimizing for change
Beyond single Agile teams to Agile Enterprises</li></li></ul><li>10-year Agile Manifesto event: goal to improve current state of Agile … not to redefine it!<br />demand technical excellence (testing, integration and design) <br />promote culture change (individual and organization) <br />maximize business value (use business priorities throughout the process)<br />organize knowledge (improve teaching and knowledge repositories)<br />10-year Agile Manifesto Workshop<br />
1) Requirements elaboration management (User Stories evolution)<br />2) Configuration management<br />3) Integration (continuous or frequent), <br />4) Layered testing for D^4 (unit, regression, system, acceptance) including daily testing reports<br />5) Agile Architecture and design, using architectural and design patterns, <br />6) Coding standards<br />Engineering Practices<br />
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.