1. Agile Architecture? Paul Lund 24 th Nov 2010

2. Agile Manifesto We 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 interactions over 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 2 Source: http://agilemanifesto.org/http://agilemanifesto.org/

3. Principles behind the Agile Manifesto 1.Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2.Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3.Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4.Business people and developers must work together daily throughout the project. 5.Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6.The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7.Working software is the primary measure of progress. 8.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9.Continuous attention to technical excellence and good design enhances agility. 10.Simplicity--the art of maximizing the amount of work not done--is essential. 11.The best architectures, requirements, and designs emerge from self-organizing teams. 12.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 3 Source: http://agilemanifesto.org/principles.htmlhttp://agilemanifesto.org/principles.html

4. What This REALLY Means? “Cheap and quick” “No need to plan, make it up as you go along” “Tactical is the way to go” “Solution architecture is irrelevant” “Enterprise architecture is REALLY irrelevant” 4

5. I’m Confused! Is Agile a “software development method” or a “systems development method” or both? Can Architecture be done in an Agile fashion? Are we talking about Solution Architecture or Enterprise Architecture or both? 5

6. Enterprise Unified Process 6 Source: http://www.enterpriseunifiedprocess.com/http://www.enterpriseunifiedprocess.com/

7. Agile Manifesto We 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 interactions over 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 7 Source: http://agilemanifesto.org/http://agilemanifesto.org/

8. Agile Manifesto v2 We are uncovering better ways of developing systems by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working solutions over comprehensive documentation Stakeholder 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 8 Source: https://www.ibm.com/developerworks/mydeveloperworks/blogs/ambler/?lang=enhttps://www.ibm.com/developerworks/mydeveloperworks/blogs/ambler/?lang=en

9. Principles behind the Agile Manifesto 1.Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. 2.Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3.Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4.Business people and developers must work together daily throughout the project. 5.Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6.The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7.Working software is the primary measure of progress. 8.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9.Continuous attention to technical excellence and good design enhances agility. 10.Simplicity--the art of maximizing the amount of work not done--is essential. 11.The best architectures, requirements, and designs emerge from self-organizing teams. 12.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 9 Source: http://agilemanifesto.org/principles.htmlhttp://agilemanifesto.org/principles.html

10. Principles Behind the Agile Manifesto v2 1.Our highest priority is to satisfy the stakeholders through early and continuous delivery of valuable solutions. 2.Welcome changing requirements, even late in the solution delivery lifecycle. Agile processes harness change for the stakeholder’s competitive advantage. 3.Deliver working solutions frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. 4.Stakeholders and developers must work together daily throughout the project. 5.Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. 6.The most efficient and effective method of conveying information to and within a delivery team is face-to-face conversation. 7.Working solutions are the primary measure of progress. 8.Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 9.Continuous attention to technical excellence and good design enhances agility. 10.Simplicity--the art of maximizing the amount of work not done--is essential. 11.The best architectures, requirements, and designs emerge from self-organizing teams. 12.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. 13.Leverage and evolve the assets within your organizational ecosystem, and collaborate with the people responsible for those assets to do so. 14.Minimize work in progress and visualize workflow. ?????? 15.The organizational ecosystem must evolve to reflect and enhance the efforts of agile teams, yet be sufficiently flexible to still support non-agile or hybrid teams. 10 Source: https://www.ibm.com/developerworks/mydeveloperworks/blogs/ambler/?lang=enhttps://www.ibm.com/developerworks/mydeveloperworks/blogs/ambler/?lang=en

11. An Agile SDLC Source: http://www.ambysoft.com/essays/agileLifecycle.htmlhttp://www.ambysoft.com/essays/agileLifecycle.html 11