architecture in the age of compositionality
play

Architecture in the Age of Compositionality Jan Bosch VP, - PowerPoint PPT Presentation

Architecture in the Age of Compositionality Jan Bosch VP, Engineering Process Professor of Software Engineering Jan@JanBosch.com May 18, 2011 Intuit Proprietary & Confidential If you are not moving at the speed of the marketplace


  1. Architecture in the Age of Compositionality Jan Bosch VP, Engineering Process Professor of Software Engineering Jan@JanBosch.com May 18, 2011 Intuit Proprietary & Confidential

  2. “If you are not moving at the speed of the marketplace you’re already dead – you just haven’t stopped breathing yet” Jack Welch 2 Intuit Proprietary & Confidential

  3. Three Key Take-Aways • Increasing SPEED trumps ANY other improvement R&D can provide to the company – it is the foundation for everything else • Software engineering is at an inflection point – from “integration-oriented” to “composition- oriented” software engineering • Software architecture is key to build delightful products in the context of software ecosystems 3 Intuit Proprietary & Confidential

  4. Overview • Vem är jag? Wie ben ik? Who am I? • Introducing Intuit • Speed matters: implications for software engineering • Building delightful products • Software ecosystems • Implications for software architecture • Conclusion Intuit Proprietary & Confidential

  5. From Research to Industry Industrial Engineering Process development (Intuit, USA) Industrial Head of research lab research (Nokia, Finland) Professor of software Academia engineering (+ consulting) (RuG, Netherlands) (Chalmers, Sweden) Intuit Proprietary & Confidential

  6. Intuit Company Information Who We Are… A leading provider of business and financial management solutions • Founded in 1983 • FY 2010 revenue of $3.5 billion • Intuit is traded on the NASDAQ: INTU • Employs around ~8,000 people • Major offices across the U.S. and in Canada and the United Kingdom • More than 50 million people use our QuickBooks, Payroll, Payments, TurboTax, Digital Insight and Quicken products and services. Intuit Proprietary & Confidential

  7. Mission: why we exist as a company… To be a premier innovative growth company that improves our customers’ financial lives so profoundly… they can’t imagine going back to the old way “Better Money Outcomes” We serve these end customers Financial… making & saving money, grow & profit Consumers Small Businesses Productivity… turning drudgery into time for what matters most …and those who serve them Compliance… without even having to think about it Health Financial Care Accountants Institutions Confidence… from the wisdom & Players experience of others 7 Intuit Proprietary & Confidential

  8. Proven formula: lots of delighted customers… Improving 50M Lives Help families find $1,000 Help small businesses be 20% annually… $400M in more profitable… Customers consumer savings revenues ~20% of U.S. GDP, pay 1 in 12 American workers Help people get the Improve FI profit per Help accountants be 20% maximum tax refund… customer by 20%… more productive today… $33B in tax refunds, IB customers equal to the Serve half of all 1 out of every 3 5 th largest U.S. bank accounting firms tax returns e-filed 8 Intuit Proprietary & Confidential

  9. Proven Formula: talented & engaged employees Most Admired: Software Industry Strong Employee Engagement Fortune Top 100 Places to Work 9 Intuit Proprietary & Confidential

  10. Secular Shifts: transforming our company… Trends Implications Intuit is driving: “Connected Services” Demographic Shifts • Software-Advantaged Services • Software-as-a-Service • Platform-as-a-Service Intuit is embracing: Value Creation Shifts Social capitalize on our large and growing customer bases to unleash the collective power of user contributions, behaviors and dat a Technology Shifts Mobile deliver “in the pocket” when that is the preferred solution Global employ the world’s talents Geographic Shifts to find & solve important problems around the globe 10 Intuit Proprietary & Confidential

  11. Overview • Vem är jag? Wie ben ik? Who am I? • Introducing Intuit • Speed matters: implications for software engineering • Building delightful products • Software ecosystems • Implications for software architecture • Conclusion Intuit Proprietary & Confidential

  12. Where are we going? How fast? Bioterial age 20 years Economic value added Information age 50 years Industrial age 360 years Agrarian age Source: “The Coming Biotech Age”, Richard W. Oliver- McGraw-Hill 6000 BC 1760 Time Intuit Proprietary & Confidential

  13. Accelerating User Adoption Value Creation Shifts Emerging companies highlight importance of user contribution and social connectedness Level of User Contribution Founded 1984 1995 2004 1M users ~6 years 30 months 10 months 50M users N/A ~80 months ~44 months Intuit Proprietary & Confidential

  14. Need for Speed in R&D – An Example • Company X: R&D is 10% of revenue, e.g. 100M$ for a 1B$ product • New product development cycle: 12 months • Alternative 1: improve efficiency of development with 10% – 10 M$ reduction in development cost • Alternative 2: reduce development cycle with 10% – 100M$ add to top line revenue (product starts to sell 1.2 months earlier) No efficiency improvement will outperform cycle time reduction Intuit Proprietary & Confidential

  15. Integration-centric software engineering software product lines global software development global R&D software ecosystems build & maintain roadmapping & req. mgmt causing s e l c y c y l r a e y unacceptable complexity and coordination cost pre-integrated products 15 Intuit Proprietary & Confidential

  16. Web 2.0 Rules to SW Development (1/2) Team size • 3x3 = 3 persons x 3 months (Google) • 2 pizza rule (Amazon) • Principle: What is required is a team, where the roles are defined and each member has the right skill for that role, and following a lean, agile, method — all focused on the customer. Release cycle • Weeks, not months • Continuous deployment • Principle: short cycles are key for agility, speed and decoupling Architecture • 3 API rule • Mash-ups and web services • Principle: architecture provides simplicity, compositionality and is designed in parallel with software development Focus on one thing: Minimize Dependencies 16 Intuit Proprietary & Confidential

  17. Web 2.0 Rules to SW Development (2/2) Requirements and Roadmapping • Each team (3 persons) announces what they intend to release • Some (QA) requirements are shared across the board, e.g. performance, latency, etc. • Principle: the cost of overlapping teams is much lower than the cost of synchronized, planned roadmaps and plans Process • CMMi and other process maturity approaches address the symptoms, not the root cause • Control is a very expensive illusion causing LOTS of inefficiency in the system • Principle: Architecture not process should manage coordination and alignment From the Cathedral to the Bazaar 17 Intuit Proprietary & Confidential

  18. Towards Composition … teams are self-selected teams can be external (2 pizza rule) (ecosystem) components are backward compatible and negotiate interfaces a r c h architecture prioritizes simplicity i t e c t u r a l c o m p o s i t i o (3 API rule) n a l i t y 18 Intuit Proprietary & Confidential

  19. Implications for Software Engineering • From process to architecture • From centralized to decentralized • From planning to experimentation • From long cycles to short cycles • From large teams to small teams • From internal to ecosystem • From CMM(I) to agile • From cathedral to bazaar 19 Intuit Proprietary & Confidential

  20. Classification – Five Approaches open ecosystem independent deployment release trains release groupings integration-centric development traditional product ecosystem development development Intuit Proprietary & Confidential

  21. Overview • Vem är jag? Wie ben ik? Who am I? • Introducing Intuit • Speed matters: implications for software engineering • Building delightful products • Software ecosystems • Implications for software architecture • Conclusion Intuit Proprietary & Confidential

  22. What Do These Product Have in Common? Intuit Proprietary & Confidential

  23. Designing Pleasurable Products Hierarchy of ”People seek pleasure” Consumer needs Jordan’s four pleasures framework (based on Tiger 1992): Physio-pleasure • Pleasure from sensory pleasure organs, e.g. tactile feedback Socio-pleasure • Enjoyment from social interactions usability Psycho-pleasure • Cognitive and emotional responses, e.g. usability Ideo-pleasure functionality • Supporting people’s values, e.g. green values Jordan, P (2002): Designing Pleasurable Products, Taylor and Francis. Intuit Proprietary & Confidential

  24. “Design for Delight” at Intuit = WOW Going beyond customer expectations in delivering ease and benefit, evoking positive emotion throughout the customer journey… …So folks buy more & tell their friends Benefit = the Growing our business is improvement in the the goal customer’s life or business outcome Intuit Proprietary & Confidential

  25. The “How” In that focus, create better solutions, Uncover what’s most within available resources important to customers } } Prototype lots Pick a Focus Observe Understand Test of Ideas Fast Iteration Repeat Intuit Design4Delight Framework Intuit Proprietary & Confidential

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend