際際滷

際際滷Share a Scribd company logo

Agile on Wall Street

Sergio Bogazzi
Sergio Bogazzi

Agiles 2008 presentation in Buenos Aires, Argentina on the cultural, managerial and engineering benefits of Agile on Wall Street at Agiles2008 the first ever Latin American conference on Agile Development methodologies. http://www.agiles2008.org/en/session.php?id=wallStreet

1 of 18
Downloaded 25 times
AGILE ON WALL STREET AGILES 2008 BUENOS AIRES, ARGENTINA OCTOBER 23, 2008 Sergio Bogazzi, The Techdoer Times 1
Computing Challenges on Wall Street Agiles Benefits vs. Predictive Methodologies Challenges Moving Forward 2008 Techdoer 2 AGILE ON WALL STREET Agenda "In today's economic environment, things change on a dime: the world's coming to an end, and all of a sudden, in 10 minutes, we're in the big rally, having that flexibility is really important. TABB Group
3 People Process Technology The last decade on Wall Street has seen the accelerated growth in high- performance electronic trading. Some of the key elements driving this growth are: AGILE ON WALL STREET People, Process, and Technology FPGA & GPUs Multi-core Traders XP Scrum RUP Waterfall Background image source: http://agilemanifesto.org/ Infiniband Proximity Hosting Regulators Broker Dealers Solid State Exchanges Investment Bankers Technologists + +
2008 Techdoer 4 AGILE ON WALL STREET Electronic Trading Simplified look at the electronic trading lifecycle: Market Data Distribution Electronic Trading Platform Order Execution Venues Options traffic in North America, has increased from 20 MBps to 600 MBps resulting in a 20x increase (from about $5,000 a month to $100,000 a month) just in raw network connectivity to handle this data load. - Savvis
2008 Techdoer 5 AGILE ON WALL STREET Development Challenges Building successful high-performance electronic trading systems on Wall Street requires nimbleness and precision with an explicit focus on: Non-functional requirements - Non-ambiguous - Complex - Frequently Changing - Directly tied to profit Chart Source: IBM ibm.com N o n F u n c t i o n a lFunctional Regulatory Performance
2008 Techdoer 6 AGILE ON WALL STREET Why Importance on Non-Functional Requirements Q: What non-functional requirements do you deal with on a day-to-day basis? Chart Source: IBM ibm.com N o n F u n c t i o n a lFunctional Regulatory Performance
Q: What challenges do software teams face on Wall Street? - Electronic tradings focus on non-functional requirements - Constant changes to regulation and trading strategies - High-pressure, high-stakes, highly-competitive, relationship-oriented industry 2008 Techdoer 7 AGILE ON WALL STREET Development Challenges "Five years ago we were talking seconds, now we're into the milliseconds, five years from now we'll probably be measuring latency in microseconds. BATS CEO Cummings Lets take a look at non-functional requirements on Wall Street
2008 Techdoer 8 Chart Source: STAC Research - http://www.stacresearch.com Low Latency - At 140,000 messages/sec, zero-message loss and mean- latency must not exceed 1.5 milliseconds. Not Good AGILE ON WALL STREET Non-Functional Requirements If a brokers electronic trading platform is 5 milliseconds behind the competition, it could lose at least 1% of its customer order flow; thats $4 million in revenues per millisecond. Up to 10 milliseconds of latency could result in a 10% drop in revenues. - TABB
2008 Techdoer 9 CPU Utilization Threshold For escalating message rates, zero-message loss, average latency under 1.5 milliseconds and aggregate CPU utilization must stay below 30% utilization. AGILE ON WALL STREET Non-Functional Requirements ..peak conditions can average 50x or more above their average 29 West Messaging Not Good
2008 Techdoer 10 Chart Source: Market Data Peaks marketdatapeaks.com High Throughput - Zero-message loss up to 1,200,000 messages/second. AGILE ON WALL STREET Non-Functional Requirements Article Source: Bloomberg.com Statements from Federal Reserve Chief around 2pm ET on October 7, 2008
2008 Techdoer 11 AGILE ON WALL STREET and more non-functional requirements If a market repeatedly does not respond within one second or less, market participants may exercise self-help and avoid that market for purposes of the Order Protection Rule transactions that are subject to NASD Rules 6130(g) and 6130 (c) and also required pursuant to an NASD trade reporting rule to be reported within 90 seconds. Some regulatory requirements from the Securities and Exchange Commission: Lets look at the development approaches behind these requirements
12 Predictive approaches rely on detailed upfront design and planning prior to implementation, followed by thoroughly documented working systems. - Industry change is frequent and lightening fast - Time is money - Trial-and-error more effective with proprietary approaches - Adapting to customers day-to-day activities is critical AGILE ON WALL STREET The Problem with Predictive Approaches Unified Process Waterfall Microsoft Solutions Framework
13 Adaptive approaches (e.g. Agile) put the customer needs, not the software requirements specification, as the ultimate measure of quality. These approaches deliver cultural, managerial and engineering benefits, empowering small teams to tackle Wall Streets toughest business problems including the performance an regulatory non-functional requirements presented here. Lets take a closer look at these benefits AGILE ON WALL STREET Benefits Behind Adaptive Approaches Test-Driven Development Extreme Programming Scrum
14 Self-Organizing Teams Attracts key individuals and puts their intrinsic motivation as the driver behind innovative, non-commoditized designs and solutions. Move People Around Helps foster individual motivation required for complex problem solving and introduces cross-training that cycles both tacit and explicit knowledge between business and technology. Embracing the Customer Is key in an industry where business and technology are so intertwined. No Overtime- In this high-stakes, high-stress industry helps avert burnout and is key toward sustainable progress. Iterative Development Inspires hard-to-get-a-hold of customers to contribute early on in the development process. Iterative lifecycle with daily meetings more closely aligned with day to day business activities - Market opens at 9:30am ET and closes at 4. AGILE ON WALL STREET Cultural Benefits of Agile Test-Driven Development Extreme Programming Scrum
15 Frequent Deliverables Mitigates the risk that complex temporal requirements wont be met. Demonstrating to customers that non-functional requirements have been implemented is harder than demonstrating successful implementation of functional requirements. Project Velocity - and other empirical productivity metrics are key to building schedules the business and development teams can trust. Product Backlog - Helps ensure highest priority needs are implemented first. Daily Meetings Introduces continuous accountability among team members. Helps identify and address risks in non-commoditized components early and often. AGILE ON WALL STREET Managerial Benefits of Agile Test-Driven Development Extreme Programming Scrum
16 Test-Driven Development Helps put a visual interface and adds much needed transparency to the implementation of non-functional requirements. Continuous Integration With performance latency measures in microseconds, for example, even the smallest code change can break non-functional requirements. CI mitigates the risk of this happening by alerting team members early and often. Collapsing Design Time Differentiation lies in the sophistication of the internals and their ability to outperform competition with respect to non-functional requirements which change often. Upfront design runs the risk of being outdated. Refactoring Empowers teams to deliver working software early while continuously evolving the codebase towards desired state. AGILE ON WALL STREET Engineering Benefits of Agile Test-Driven Development Extreme Programming Scrum
2008 Techdoer 17 AGILE ON WALL STREET Agiles Future Challenges - Parallel Computing - Test runs that measure in minutes and hours versus seconds - Integrating managed service providers - Evolving TDD for Non-Functional Requirements - Evolving TDD for Distributed/Managed Systems - Agile for Distributed Teams - New regulations set to take over Wall Street
Download presentation at: The Techdoer Times - http://techdoer.com 18 AGILE ON WALL STREET Thank You

More Related Content

Agile on Wall Street

  • 1. AGILE ON WALL STREET AGILES 2008 BUENOS AIRES, ARGENTINA OCTOBER 23, 2008 Sergio Bogazzi, The Techdoer Times 1
  • 2. Computing Challenges on Wall Street Agiles Benefits vs. Predictive Methodologies Challenges Moving Forward 2008 Techdoer 2 AGILE ON WALL STREET Agenda "In today's economic environment, things change on a dime: the world's coming to an end, and all of a sudden, in 10 minutes, we're in the big rally, having that flexibility is really important. TABB Group
  • 3. 3 People Process Technology The last decade on Wall Street has seen the accelerated growth in high- performance electronic trading. Some of the key elements driving this growth are: AGILE ON WALL STREET People, Process, and Technology FPGA & GPUs Multi-core Traders XP Scrum RUP Waterfall Background image source: http://agilemanifesto.org/ Infiniband Proximity Hosting Regulators Broker Dealers Solid State Exchanges Investment Bankers Technologists + +
  • 4. 2008 Techdoer 4 AGILE ON WALL STREET Electronic Trading Simplified look at the electronic trading lifecycle: Market Data Distribution Electronic Trading Platform Order Execution Venues Options traffic in North America, has increased from 20 MBps to 600 MBps resulting in a 20x increase (from about $5,000 a month to $100,000 a month) just in raw network connectivity to handle this data load. - Savvis
  • 5. 2008 Techdoer 5 AGILE ON WALL STREET Development Challenges Building successful high-performance electronic trading systems on Wall Street requires nimbleness and precision with an explicit focus on: Non-functional requirements - Non-ambiguous - Complex - Frequently Changing - Directly tied to profit Chart Source: IBM ibm.com N o n F u n c t i o n a lFunctional Regulatory Performance
  • 6. 2008 Techdoer 6 AGILE ON WALL STREET Why Importance on Non-Functional Requirements Q: What non-functional requirements do you deal with on a day-to-day basis? Chart Source: IBM ibm.com N o n F u n c t i o n a lFunctional Regulatory Performance
  • 7. Q: What challenges do software teams face on Wall Street? - Electronic tradings focus on non-functional requirements - Constant changes to regulation and trading strategies - High-pressure, high-stakes, highly-competitive, relationship-oriented industry 2008 Techdoer 7 AGILE ON WALL STREET Development Challenges "Five years ago we were talking seconds, now we're into the milliseconds, five years from now we'll probably be measuring latency in microseconds. BATS CEO Cummings Lets take a look at non-functional requirements on Wall Street
  • 8. 2008 Techdoer 8 Chart Source: STAC Research - http://www.stacresearch.com Low Latency - At 140,000 messages/sec, zero-message loss and mean- latency must not exceed 1.5 milliseconds. Not Good AGILE ON WALL STREET Non-Functional Requirements If a brokers electronic trading platform is 5 milliseconds behind the competition, it could lose at least 1% of its customer order flow; thats $4 million in revenues per millisecond. Up to 10 milliseconds of latency could result in a 10% drop in revenues. - TABB
  • 9. 2008 Techdoer 9 CPU Utilization Threshold For escalating message rates, zero-message loss, average latency under 1.5 milliseconds and aggregate CPU utilization must stay below 30% utilization. AGILE ON WALL STREET Non-Functional Requirements ..peak conditions can average 50x or more above their average 29 West Messaging Not Good
  • 10. 2008 Techdoer 10 Chart Source: Market Data Peaks marketdatapeaks.com High Throughput - Zero-message loss up to 1,200,000 messages/second. AGILE ON WALL STREET Non-Functional Requirements Article Source: Bloomberg.com Statements from Federal Reserve Chief around 2pm ET on October 7, 2008
  • 11. 2008 Techdoer 11 AGILE ON WALL STREET and more non-functional requirements If a market repeatedly does not respond within one second or less, market participants may exercise self-help and avoid that market for purposes of the Order Protection Rule transactions that are subject to NASD Rules 6130(g) and 6130 (c) and also required pursuant to an NASD trade reporting rule to be reported within 90 seconds. Some regulatory requirements from the Securities and Exchange Commission: Lets look at the development approaches behind these requirements
  • 12. 12 Predictive approaches rely on detailed upfront design and planning prior to implementation, followed by thoroughly documented working systems. - Industry change is frequent and lightening fast - Time is money - Trial-and-error more effective with proprietary approaches - Adapting to customers day-to-day activities is critical AGILE ON WALL STREET The Problem with Predictive Approaches Unified Process Waterfall Microsoft Solutions Framework
  • 13. 13 Adaptive approaches (e.g. Agile) put the customer needs, not the software requirements specification, as the ultimate measure of quality. These approaches deliver cultural, managerial and engineering benefits, empowering small teams to tackle Wall Streets toughest business problems including the performance an regulatory non-functional requirements presented here. Lets take a closer look at these benefits AGILE ON WALL STREET Benefits Behind Adaptive Approaches Test-Driven Development Extreme Programming Scrum
  • 14. 14 Self-Organizing Teams Attracts key individuals and puts their intrinsic motivation as the driver behind innovative, non-commoditized designs and solutions. Move People Around Helps foster individual motivation required for complex problem solving and introduces cross-training that cycles both tacit and explicit knowledge between business and technology. Embracing the Customer Is key in an industry where business and technology are so intertwined. No Overtime- In this high-stakes, high-stress industry helps avert burnout and is key toward sustainable progress. Iterative Development Inspires hard-to-get-a-hold of customers to contribute early on in the development process. Iterative lifecycle with daily meetings more closely aligned with day to day business activities - Market opens at 9:30am ET and closes at 4. AGILE ON WALL STREET Cultural Benefits of Agile Test-Driven Development Extreme Programming Scrum
  • 15. 15 Frequent Deliverables Mitigates the risk that complex temporal requirements wont be met. Demonstrating to customers that non-functional requirements have been implemented is harder than demonstrating successful implementation of functional requirements. Project Velocity - and other empirical productivity metrics are key to building schedules the business and development teams can trust. Product Backlog - Helps ensure highest priority needs are implemented first. Daily Meetings Introduces continuous accountability among team members. Helps identify and address risks in non-commoditized components early and often. AGILE ON WALL STREET Managerial Benefits of Agile Test-Driven Development Extreme Programming Scrum
  • 16. 16 Test-Driven Development Helps put a visual interface and adds much needed transparency to the implementation of non-functional requirements. Continuous Integration With performance latency measures in microseconds, for example, even the smallest code change can break non-functional requirements. CI mitigates the risk of this happening by alerting team members early and often. Collapsing Design Time Differentiation lies in the sophistication of the internals and their ability to outperform competition with respect to non-functional requirements which change often. Upfront design runs the risk of being outdated. Refactoring Empowers teams to deliver working software early while continuously evolving the codebase towards desired state. AGILE ON WALL STREET Engineering Benefits of Agile Test-Driven Development Extreme Programming Scrum
  • 17. 2008 Techdoer 17 AGILE ON WALL STREET Agiles Future Challenges - Parallel Computing - Test runs that measure in minutes and hours versus seconds - Integrating managed service providers - Evolving TDD for Non-Functional Requirements - Evolving TDD for Distributed/Managed Systems - Agile for Distributed Teams - New regulations set to take over Wall Street
  • 18. Download presentation at: The Techdoer Times - http://techdoer.com 18 AGILE ON WALL STREET Thank You