Sally Elatta & Kyle Gabhart Comparing and Contrasting  Agile and SOA
<ul><li>Kyle Gabhart  [email_address]   </li></ul><ul><li>Subject matter expert in the area of SOA and Enterprise Architec...
<ul><li>Comparing SOA to Agile – Apples and Oranges?  </li></ul><ul><li>The Agile Story </li></ul><ul><li>The SOA Story </...
<ul><li>Agile   is a  Software Development & Execution methodology  that aims to improve how software projects are execute...
<ul><li>The manifesto’s shared value statement: “We are uncovering better ways of developing software by doing it and help...
Copyright(c) Sally Elatta 2009
Copyright(c) Sally Elatta 2009  Product Backlog Co-Development Business / IT as One Team Measurement! Cross Functional Team
<ul><li>Traditional Architecture ..  </li></ul>Copyright © Sun Microsystems  Data Warehouse Legacy Mainframes Web Servers ...
 
Order Services Customer Services Product Services <ul><li>PlaceOrder </li></ul><ul><li>GetOrderStatus </li></ul><ul><li>Ca...
<ul><li>Architecture Goal </li></ul>Copyright © Sun Microsystems  Legacy Mainframes Web Servers Report Server Enterprise I...
Copyright(c) Sally Elatta 2009
Copyright(c) Sally Elatta 2009  SOA Agile Align with the Business Needs Facilitated through layered services and service o...
<ul><li>SOA projects tend to suffer from BDUF (Big Design Upfront). </li></ul><ul><li>Usually implemented top down with a ...
<ul><li>Challenge:  SOA projects tend to suffer from BDUF (Big Design Upfront). </li></ul><ul><ul><li>Perform high level e...
<ul><li>Challenge:  SOA assumes services will be designed correctly the first time and does not deal well with iterative c...
<ul><li>Thought to be a fit for small projects. </li></ul><ul><li>Lacks proper upfront architecture. </li></ul><ul><li>Ver...
<ul><li>Big Design  and Architecture upfront is not good from an Agile perspective, but so is  NO upfront architecture  an...
<ul><li>During iteration 0, the Agile Architect should attempt to identify high risks and create  Proof of Concept  storie...
Business Process Modeling Service Identification & Specification  Service Implementation Testing, Refactoring Final Testin...
Copyright(c) Sally Elatta 2009  <ul><li>Agile Training & Coaching </li></ul><ul><li>Executive and Business Overview of Agi...
<ul><li>www.WebAgeSolutions.com   </li></ul><ul><ul><li>1 877-517-6540 </li></ul></ul><ul><li>www.AgileTransformation.com ...
<ul><li>Sally’s Agile Adoption Article:  http:// tinyurl.com/6h5mam   </li></ul><ul><li>Towards an Agile Architecture: htt...
Upcoming SlideShare
Loading in …5
×

Agile and SOA Comparing the Two

3,343 views

Published on

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

Published in: Technology, Business
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,343
On SlideShare
0
From Embeds
0
Number of Embeds
966
Actions
Shares
0
Downloads
147
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide
  • Copyright (c) 2009 Sally Elatta. Do not distribute or copy without authorization.
  • Eat the elephant all at once! Different Roles work in Silos Heavy on Documentation, Light on Demonstrations Low customer collaboration Low cross-functional team collaboration Customer feedback at end resulting in bugs All or nothing delivery Customers not happy.. Why? Delayed Delivery Product Not Meeting Expectations Customer Needs Changed Lots of bugs!
  • Copyright (c) 2009 Sally Elatta. Do not distribute or copy without authorization.
  • Agile and SOA Comparing the Two

    1. 1. Sally Elatta & Kyle Gabhart Comparing and Contrasting Agile and SOA
    2. 2. <ul><li>Kyle Gabhart [email_address] </li></ul><ul><li>Subject matter expert in the area of SOA and Enterprise Architecture. </li></ul><ul><li>Popular speaker recognized for his enthusiasm and dynamic analysis of emerging technologies. </li></ul><ul><li>Authored several articles and a popular book SOA: A Field Guide for Executives </li></ul><ul><li>Director of Emerging Technologies for Web Age Solutions </li></ul><ul><li>Sally Elatta [email_address] </li></ul><ul><li>Agile /Process Improvement Coach, Architect, Trainer </li></ul><ul><li>Passionate about process improvement and building high performing teams. </li></ul><ul><li>Coached and trained many small and large organizations on Agile Adoption. </li></ul><ul><li>Certified ScrumMaster, Scrum Practitioner, IBM, Sun, and Microsoft Certifications. </li></ul>Copyright(c) Sally Elatta 2009
    3. 3. <ul><li>Comparing SOA to Agile – Apples and Oranges? </li></ul><ul><li>The Agile Story </li></ul><ul><li>The SOA Story </li></ul><ul><li>How Do They Relate? </li></ul><ul><li>The Challenges/Misconceptions with Both </li></ul><ul><li>Bringing more Agility to SOA Projects </li></ul><ul><li>Bringing better Architecture to Agile Projects </li></ul><ul><li>Conclusion </li></ul>Copyright(c) Sally Elatta 2009
    4. 4. <ul><li>Agile is a Software Development & Execution methodology that aims to improve how software projects are executed. It provides simple yet effective project management and engineering best practices. </li></ul><ul><li>Iterative Development Collaboration Visibility </li></ul><ul><li>Inspect & Adapt Test Driven Development Measurement </li></ul><ul><li>SOA is an Architectural Style that aims to build software services that are technology agnostic, business focused, reusable and that offer business process flexibility. </li></ul><ul><li>Services Processes Business and IT Alignment </li></ul><ul><li>Business Process Orchestration Governance Integration </li></ul>Copyright(c) Sally Elatta 2009
    5. 5. <ul><li>The manifesto’s shared value statement: “We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: </li></ul>“ That is, while there is value in the items on the right, we value the items on the left more.” Copyright(c) Sally Elatta 2009 Individuals & interactions Over Processes & Tools Working Software Over Comprehensive Documentation Customer Collaboration Over Contract Negotiation Responding to Change Over Following a Plan
    6. 6. Copyright(c) Sally Elatta 2009
    7. 7. Copyright(c) Sally Elatta 2009 Product Backlog Co-Development Business / IT as One Team Measurement! Cross Functional Team
    8. 8. <ul><li>Traditional Architecture .. </li></ul>Copyright © Sun Microsystems Data Warehouse Legacy Mainframes Web Servers Application Servers Application Servers Workstation Report Server Data Marts Data Marts Data Data Data
    9. 10. Order Services Customer Services Product Services <ul><li>PlaceOrder </li></ul><ul><li>GetOrderStatus </li></ul><ul><li>CalcOrderTotal </li></ul><ul><li>GetOrderDetails </li></ul><ul><li>GetCustomerInfo </li></ul><ul><li>AddNewCustomer </li></ul><ul><li>UpdateCustomerInfo </li></ul><ul><li>GetAllCustomers </li></ul><ul><li>GetProductCatalog </li></ul><ul><li>GetProductDetail </li></ul><ul><li>AddNewProduct </li></ul><ul><li>CheckInventoryLevel </li></ul>
    10. 11. <ul><li>Architecture Goal </li></ul>Copyright © Sun Microsystems Legacy Mainframes Web Servers Report Server Enterprise Interoperability Hub (Service Bus) Workstation Application Servers Application Servers Data Data Data Data Marts Data Marts Data Warehouse Exposed Service Exposed Service Exposed Service Exposed Service Exposed Service
    11. 12. Copyright(c) Sally Elatta 2009
    12. 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
    13. 14. <ul><li>SOA projects tend to suffer from BDUF (Big Design Upfront). </li></ul><ul><li>Usually implemented top down with a divide and conquer approach. </li></ul><ul><li>Long time before any immediate ROI is realized. </li></ul><ul><li>SOA assumes services will be designed correctly the first time and does not deal well with iterative changes. </li></ul><ul><li>Communication done extensively via heavy documentation. </li></ul>Copyright(c) Sally Elatta 2009
    14. 15. <ul><li>Challenge: SOA projects tend to suffer from BDUF (Big Design Upfront). </li></ul><ul><ul><li>Perform high level enterprise framework design upfront then dive into detail design iteratively. </li></ul></ul><ul><li>Challenge: Usually implemented top down with a divide and conquer approach. </li></ul><ul><ul><li>Create collaborative cross functional teams with heavy business engagement. </li></ul></ul><ul><li>Challenge: Long time before any immediate ROI is realized. </li></ul><ul><ul><li>Direct customer involvement combined with early delivery of service functionality within each iteration produces value more rapidly. </li></ul></ul>Copyright(c) Web Age Solutions
    15. 16. <ul><li>Challenge: SOA assumes services will be designed correctly the first time and does not deal well with iterative changes. </li></ul><ul><ul><li>Proper service interface design, service contract management, thorough service version strategies, and effective use of intermediaries can produce very robust and adaptable service interfaces. </li></ul></ul><ul><li>Challenge: Communication done exclusively via heavy documentation. </li></ul><ul><ul><li>Well-designed service-oriented enterprises heavily leverage metadata, which is automatically generated and maintained by tools and through proper governance and represents a “self-documenting” approach </li></ul></ul>Copyright(c) Web Age Solutions
    16. 17. <ul><li>Thought to be a fit for small projects. </li></ul><ul><li>Lacks proper upfront architecture. </li></ul><ul><li>Very little formal documentation. </li></ul><ul><li>Lacks proper upfront planning. </li></ul><ul><li>Is not prescriptive, does not lay out all steps and deliverables needed upfront. </li></ul>Copyright(c) Sally Elatta 2009
    17. 18. <ul><li>Big Design and Architecture upfront is not good from an Agile perspective, but so is NO upfront architecture and design! </li></ul><ul><li>Agile projects need to do High Level Architecture envisioning upfront during Iteration 0 . </li></ul><ul><li>Detailed architecture and service implementation can be done iteratively . </li></ul><ul><li>An Agile Architect /team lead must coach the team through design meetings each iteration. </li></ul><ul><li>Code review sessions should be integrated in each iteration. Pair/Collaborative Programming . </li></ul><ul><li>Iteration 0 training on standards for coding, design packaging, deployment, naming ..etc. </li></ul>Copyright(c) Sally Elatta 2009
    18. 19. <ul><li>During iteration 0, the Agile Architect should attempt to identify high risks and create Proof of Concept stories that mitigate them. </li></ul><ul><li>Do collaborative design instead of ivory tower architectures. You still have an architecture owner for final decisions. </li></ul><ul><li>Use lots of understandable models and diagrams. Communicate them visibility. </li></ul><ul><li>Requirements and business value should drive your architecture not the drive to use specific technologies and tools. </li></ul><ul><li>Do not ‘ over architect ’ and over use ‘patterns’. </li></ul>Copyright(c) Sally Elatta 2009
    19. 20. Business Process Modeling Service Identification & Specification Service Implementation Testing, Refactoring Final Testing Service Deployment
    20. 21. Copyright(c) Sally Elatta 2009 <ul><li>Agile Training & Coaching </li></ul><ul><li>Executive and Business Overview of Agile/Lean </li></ul><ul><li>Real World Agile and Scrum team training + Project Jump Start </li></ul><ul><li>Agile Engineering Practices </li></ul><ul><li>Advanced Agile Topics </li></ul><ul><li>Effective/Agile Requirements Gathering </li></ul><ul><li>Servant Leadership </li></ul><ul><li>… More! </li></ul>
    21. 22. <ul><li>www.WebAgeSolutions.com </li></ul><ul><ul><li>1 877-517-6540 </li></ul></ul><ul><li>www.AgileTransformation.com </li></ul><ul><ul><li>1 402-212-3211 </li></ul></ul>Copyright(c) Sally Elatta 2009
    22. 23. <ul><li>Sally’s Agile Adoption Article: http:// tinyurl.com/6h5mam </li></ul><ul><li>Towards an Agile Architecture: http://tinyurl.com/c3f3uz </li></ul><ul><li>Kyle’s SOA Guide for Executive Book: http://tinyurl.com/ykj3zjc </li></ul><ul><li>Kyle’s Articles: http://kylegabhart.sys-con.com/ </li></ul>

    ×