Yes, both of them are buzz words, but when you peel back the buzz, what is the true value that lies behind both of these methods? How do they compare and how do they differ? Most importantly, how can we bring about Agility to SOA projects and how can better architecture be applied to Agile projects? Me and Kyle also discussed some of the challenges with attempting iterative development on SOA projects and provided some ways both can leverage each other's strengths. Want this seminar presented at YOUR organization? just email sally@agiletransformation.com www.AgileTransformation.com

1. Sally Elatta & Kyle Gabhart Comparing and Contrasting Agile and SOA

6. Copyright(c) Sally Elatta 2009

7. Copyright(c) Sally Elatta 2009 Product Backlog Co-Development Business / IT as One Team Measurement! Cross Functional Team

12. Copyright(c) Sally Elatta 2009

13. Copyright(c) Sally Elatta 2009 SOA Agile Align with the Business Needs Facilitated through layered services and service orchestration Empowered Product Owner, Team works on highest priority user stories, not ‘Done’ until user acceptance Provide Flexibility and Adaptation Through loosely coupled service interfaces and policy-driven business rules New stories are welcome (following set rules), retrospective allows process inspection and adaption Produce quick ROI By reducing dependence upon expensive middleware licensing and also through re-configuring solutions Customer views working software quickly, customer may deploy small features that are valuable Respond to Change Re-deploying services, re-configuring business processes, or changing policies Reviewing the plan each iteration, story reprioritization based on business needs

20. Business Process Modeling Service Identification & Specification Service Implementation Testing, Refactoring Final Testing Service Deployment