Agile SOA:Application development in the new enterprise24 May 2010<br />Paulo Rosado<br />
Traditional<br />
$1<br />Analysis<br />Design<br />Development<br />10x – 50x<br />more <br />expensive<br />Testing<br />3-6 months<br />6...
Agile works better<br />
Agile Do things incrementallyInvolve the business continuously Release, asap<br />
$1<br />3x – 5x<br />2 weeks<br />2 weeks<br />2 weeks<br />2 weeks<br />2 weeks<br />Agile Methodologies<br />Projects ar...
Less software“45% of features will never be used. I wish I knew which ones”<br />Source:Standish Group Study Reported at X...
Functional softwareExactly what is needed.<br />
Reprioritize features for next sprint<br />
Flexible softwareAligned with Business Changes<br />
Adopted softwareFlexibility is extended into roll-out phases<br />
Tune application after launch<br />
IT becomes a Strategic asset… instead of a cost center<br />
Agile is hard<br />
“don’t ever mention that again around here […] agile is a banned word in this organization”<br />
Tools + <br />infrastructure<br />Architecture<br />SOA<br />Process<br />agile<br />People<br />
SOABreak software in state full componentsConnect loosely Use one common protocol<br />
ExampleCustomer Portal<br />
Existing systems<br />Customer Portal<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<...
Different teams<br />Customer Portal<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<b...
SOA architecture <br />front-end<br />composite<br />Show Products<br />back-end<br />composite<br />or<br />service<br />...
Different SLAsCache data in the service, periodically<br />Show Products<br />24 by 7<br />ProductService<br />Products<br...
Different SLAsService needs to scale<br />Show Products<br />500 requests/sec<br />ProductService<br />Products<br />Cache...
New data neededNot possible to add it to legacy Master of Records<br />Show Products<br />Photos<br />Descriptions<br />Pr...
New data needs managementBackoffice of the Portal?<br />Show Products<br />Online Product Mngmt<br />Photos<br />Descripti...
SOA architectureInside the Service?<br />Show Products<br />Online Product Mngmt<br />ProductService<br />Photos<br />Desc...
SOA frameworkMust-have capabilities<br /><ul><li> WS protocols
 Logic
 Scalable
 Integration
 Database
 Scheduling
…and more.</li></ul>Show Products<br />Online Product Mngmt<br />ProductService<br />Photos<br />Descriptions<br />Product...
Front-End Composites frameworksObvious capabilities - mashups<br /><ul><li> Web 2.0
 Logic
 WS protocols
 Scalable
…and more.</li></ul>Customer Portal<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Cata...
New data keeps pilling upNot obvious it should be added to a Service<br />Customer<br />Tracking<br />Customer Portal<br /...
Workflows & notifications<br />Emails w/ order updates<br />Customer Portal<br />Order<br />Service<br />Order<br />Manage...
Front-End Composite frameworksExtra capabilities<br /><ul><li> …
Database
 Workflows
 Notifications</li></ul>Customer Portal<br />Order<br />Service<br />Product<br />Service<br />Order<br />Management<br />...
The impact of Agile<br />
Changes ripple through the whole architecture<br />
Different teams. Different processes<br />Customer Portal<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<...
Speed is driven by the slowest<br />Show Products<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Pro...
Most effective scenario<br />Show Products<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br...
Continuous integration is a must<br />
Automatebuild/test/staging/deploy<br />
Performance & ScalabilityWhat happens when a web page takes 5 sec to render?<br />
Multiple choke pointsInstrument all dependencies<br />Infrastructure<br />collapse?<br />Customer Portal<br />Slow db <br ...
Architecture is driven by project needs<br />
Front-ends “attract” functionality<br />
Refactor Services out of the Composites<br />Customer<br />Tracking<br />Customer Portal<br />Call Center<br />Customer<br...
On-demand SOABottom-up instead of top-down<br />
 Agile SOA When you reach a tipping point<br />
Agile SOA Services/composites are categorized in “fast” and “slow” change<br />
Agile SOA Projects decrease in Time and Effort<br />
Agile SOA 3 classes of teams<br />SOA Governance tools<br />Project Management<br />
Agile SOA Managing change backlog is organized by business line<br />
Agile SOA Excels are sucked into central databases<br />
Agile SOA Hidden legacy data is sucked into services<br />
Upcoming SlideShare
Loading in …5
×

Agile SOA: application development in the new enterprise

2,920 views

Published on

In the quest for more flexibility, business alignment and speed, enterprise ITs worldwide are adopting SOA to guide their new generation of enterprise architectures. At the same time the constant realignment demanded on enterprise software to fulfill business changes is putting more pressure on IT to replace long winded projects with short, incremental releases delivered using Agile Methodologies. In this talk we will leverage on the experience of delivering more than 500 agile projects in 16 industries to describe the good and the bad of agile when deployed strategically across the enterprise. We will also present several examples of the way enterprises have converted their enterprise architectures using SOA principles to cope with an agile approach to software delivery.
This presentation was delivered during the Finco 2010 conference, organized by the Sonae Group.

Published in: Technology, Business
1 Comment
6 Likes
Statistics
Notes
No Downloads
Views
Total views
2,920
On SlideShare
0
From Embeds
0
Number of Embeds
382
Actions
Shares
0
Downloads
80
Comments
1
Likes
6
Embeds 0
No embeds

No notes for slide

Agile SOA: application development in the new enterprise

  1. 1. Agile SOA:Application development in the new enterprise24 May 2010<br />Paulo Rosado<br />
  2. 2. Traditional<br />
  3. 3. $1<br />Analysis<br />Design<br />Development<br />10x – 50x<br />more <br />expensive<br />Testing<br />3-6 months<br />6-12 months<br />
  4. 4. Agile works better<br />
  5. 5. Agile Do things incrementallyInvolve the business continuously Release, asap<br />
  6. 6. $1<br />3x – 5x<br />2 weeks<br />2 weeks<br />2 weeks<br />2 weeks<br />2 weeks<br />Agile Methodologies<br />Projects are delivered incrementally. Software gets corrected constantly based on Business Users feedback.<br />
  7. 7. Less software“45% of features will never be used. I wish I knew which ones”<br />Source:Standish Group Study Reported at XP2002 by Jim Johnson, Chairman<br />
  8. 8. Functional softwareExactly what is needed.<br />
  9. 9. Reprioritize features for next sprint<br />
  10. 10. Flexible softwareAligned with Business Changes<br />
  11. 11. Adopted softwareFlexibility is extended into roll-out phases<br />
  12. 12. Tune application after launch<br />
  13. 13. IT becomes a Strategic asset… instead of a cost center<br />
  14. 14. Agile is hard<br />
  15. 15. “don’t ever mention that again around here […] agile is a banned word in this organization”<br />
  16. 16. Tools + <br />infrastructure<br />Architecture<br />SOA<br />Process<br />agile<br />People<br />
  17. 17. SOABreak software in state full componentsConnect loosely Use one common protocol<br />
  18. 18. ExampleCustomer Portal<br />
  19. 19. Existing systems<br />Customer Portal<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  20. 20. Different teams<br />Customer Portal<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  21. 21. SOA architecture <br />front-end<br />composite<br />Show Products<br />back-end<br />composite<br />or<br />service<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  22. 22. Different SLAsCache data in the service, periodically<br />Show Products<br />24 by 7<br />ProductService<br />Products<br />Cache<br />Order<br />Management<br />(ERP)<br />9 to 5<br />
  23. 23. Different SLAsService needs to scale<br />Show Products<br />500 requests/sec<br />ProductService<br />Products<br />Cache<br />Order<br />Management<br />(ERP)<br />10 trans/sec <br />
  24. 24. New data neededNot possible to add it to legacy Master of Records<br />Show Products<br />Photos<br />Descriptions<br />ProductService<br />Products<br />Cache<br />Order<br />Management<br />(ERP)<br />Too much change. Not possible!<br />
  25. 25. New data needs managementBackoffice of the Portal?<br />Show Products<br />Online Product Mngmt<br />Photos<br />Descriptions<br />ProductService<br />Products<br />Cache<br />Order<br />Management<br />(ERP)<br />Too much change. Not possible!<br />
  26. 26. SOA architectureInside the Service?<br />Show Products<br />Online Product Mngmt<br />ProductService<br />Photos<br />Descriptions<br />Products<br />Cache<br />Order<br />Management<br />(ERP)<br />Too much change. Not possible!<br />
  27. 27. SOA frameworkMust-have capabilities<br /><ul><li> WS protocols
  28. 28. Logic
  29. 29. Scalable
  30. 30. Integration
  31. 31. Database
  32. 32. Scheduling
  33. 33. …and more.</li></ul>Show Products<br />Online Product Mngmt<br />ProductService<br />Photos<br />Descriptions<br />Products<br />Cache<br />Order<br />Management<br />(ERP)<br />Too much change. Not possible!<br />
  34. 34. Front-End Composites frameworksObvious capabilities - mashups<br /><ul><li> Web 2.0
  35. 35. Logic
  36. 36. WS protocols
  37. 37. Scalable
  38. 38. …and more.</li></ul>Customer Portal<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  39. 39. New data keeps pilling upNot obvious it should be added to a Service<br />Customer<br />Tracking<br />Customer Portal<br />Wish List<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  40. 40. Workflows & notifications<br />Emails w/ order updates<br />Customer Portal<br />Order<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  41. 41. Front-End Composite frameworksExtra capabilities<br /><ul><li> …
  42. 42. Database
  43. 43. Workflows
  44. 44. Notifications</li></ul>Customer Portal<br />Order<br />Service<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  45. 45. The impact of Agile<br />
  46. 46. Changes ripple through the whole architecture<br />
  47. 47. Different teams. Different processes<br />Customer Portal<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  48. 48. Speed is driven by the slowest<br />Show Products<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  49. 49. Most effective scenario<br />Show Products<br />Product<br />Service<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  50. 50. Continuous integration is a must<br />
  51. 51. Automatebuild/test/staging/deploy<br />
  52. 52. Performance & ScalabilityWhat happens when a web page takes 5 sec to render?<br />
  53. 53. Multiple choke pointsInstrument all dependencies<br />Infrastructure<br />collapse?<br />Customer Portal<br />Slow db <br />access?<br />Slow <br />service?<br />ProductService<br />Slow legacy access?<br />Order<br />Management<br />(ERP)<br />9 to 5<br />
  54. 54. Architecture is driven by project needs<br />
  55. 55. Front-ends “attract” functionality<br />
  56. 56. Refactor Services out of the Composites<br />Customer<br />Tracking<br />Customer Portal<br />Call Center<br />Customer<br />Service<br />Product<br />Service<br />Customer<br />Tracking<br />… and more.<br />Order<br />Management<br />(ERP)<br />Product<br />Catalog<br />(custom build)<br />
  57. 57. On-demand SOABottom-up instead of top-down<br />
  58. 58. Agile SOA When you reach a tipping point<br />
  59. 59. Agile SOA Services/composites are categorized in “fast” and “slow” change<br />
  60. 60. Agile SOA Projects decrease in Time and Effort<br />
  61. 61. Agile SOA 3 classes of teams<br />SOA Governance tools<br />Project Management<br />
  62. 62. Agile SOA Managing change backlog is organized by business line<br />
  63. 63. Agile SOA Excels are sucked into central databases<br />
  64. 64. Agile SOA Hidden legacy data is sucked into services<br />
  65. 65. Agile SOA Real-time reporting<br />Analytics<br />
  66. 66. Agile SOA successTechnology vs. People<br />
  67. 67. <ul><li> Business centric
  68. 68. Stable team
  69. 69. Senior people
  70. 70. Collaborative
  71. 71. Communication
  72. 72. Scalable
  73. 73. SOA governance
  74. 74. Refactoring
  75. 75. Integrated life cycle
  76. 76. Performance Instrumentation & Management
  77. 77. Project Management
  78. 78. Web 2.0
  79. 79. Workflow/Processes
  80. 80. Biz Logic
  81. 81. Integration
  82. 82. Database
  83. 83. WS protocols
  84. 84. Scheduling
  85. 85. Notifications</li></ul>Technology vs. People<br />
  86. 86. OutSystemsMarketing Pitch<br />
  87. 87.
  88. 88. Where does it fit?<br />
  89. 89. The Agile PlatformFront-end Web 2.0 enterprise applications<br />agileplatform<br />
  90. 90. The Agile PlatformComplete Agile SOA platform<br />agileplatform<br />
  91. 91. The Agile PlatformCoexist with ESBs<br />agileplatform<br />Enterprise Service Bus<br />agileplatform<br />
  92. 92. The Agile PlatformCoexist with BPMS<br />BPMS<br />agileplatform<br />Enterprise Service Bus<br />agileplatform<br />
  93. 93. Customers<br />135 enterprises in 16 industries (7 countries)<br />
  94. 94.
  95. 95. Over 600 apps delivered<br />
  96. 96. Thank you.Get this presentation athttp://bit.ly/agile-soapaulo.rosado@outsystems.com<br />

×