Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Vittorio Viarengo, ViVi software


Published on

Published in: Technology
  • Be the first to comment

Vittorio Viarengo, ViVi software

  1. 1. Vittorio Viarengo Vice President Development Service Delivery Platform Oracle Fusion Middleware [email_address]
  2. 2. <ul><li>The information and statements contained in this presentation represent Vittorio Viarengo’s own point of view and opinions. They do NOT represent in anyway Oracle’s official position </li></ul>
  3. 3. Buon Pomeriggio
  4. 4. Agenda <ul><li>From “Zena” to Silicon Valley </li></ul><ul><ul><li>Lessons Learned </li></ul></ul><ul><li>Creating High Performance Teams to Develop Innovative Products </li></ul><ul><ul><li>Idea </li></ul></ul><ul><ul><li>Team </li></ul></ul><ul><ul><li>Vision </li></ul></ul><ul><ul><li>Process </li></ul></ul><ul><li>Conclusions </li></ul><ul><li>Q&A </li></ul>
  5. 5. From Zena….
  6. 6. You Are Here
  7. 7. 1988-1992 L’universita’ ed l’ITD-CNR <ul><li>Corso di Ingegneria del Software </li></ul><ul><ul><li>Proff. Giorgio Olimpo, Direttore Istituto Tecnologie Didattiche CNR </li></ul></ul><ul><li>Borsa di Studio CNR </li></ul><ul><ul><li>Incontro con Carlo Innocenti (Minollo)‏ </li></ul></ul><ul><li>Il Progetti Europei OSCAR e DISCOURSE </li></ul><ul><ul><li>l’utilizzo di database Multimediali per supporto allo sviluppo di materiale didattico </li></ul></ul><ul><li>Mandato della Comunita’ Europea di usare un Object Oriented Database </li></ul><ul><ul><li>ObjectStore from Object Design </li></ul></ul>
  8. 8. The New Idea/Product Template <ul><li>Inflection Point </li></ul><ul><ul><li>Object Database Technology </li></ul></ul><ul><li>Customer Need </li></ul><ul><ul><li>Better Productivity with Object Dabases </li></ul></ul><ul><li>Product Idea/Vision </li></ul><ul><ul><li>Do for Object Databases what Standard Query Tools did to SQL databases </li></ul></ul><ul><li>Team </li></ul><ul><ul><li>Carlo Innocenti and the ITD team </li></ul></ul><ul><li>Execution </li></ul><ul><ul><li>Passion </li></ul></ul>
  9. 9. Early Lessons <ul><li>Identify Opportunities </li></ul><ul><ul><li>Learning opportunity </li></ul></ul><ul><li>Embrace Change </li></ul><ul><li>Identify Mentors </li></ul><ul><ul><li>Luigi Sarti, Augusto Chioccariello, Mauro Tavella, Giorgio Olimpo, Michela Ott, Donatella Persico </li></ul></ul><ul><li>… and Team </li></ul><ul><ul><li>Carlo Innocenti </li></ul></ul>
  10. 10. 1993 <ul><li>Prototype Ready </li></ul><ul><li>Demo sent to Object Design </li></ul><ul><li>Invitation to Object Design User Conference in Boston </li></ul><ul><ul><li>“ Meet the customer” </li></ul></ul><ul><li>Object Design Rejection… </li></ul><ul><li>Customer Encouragement </li></ul><ul><li>External Inflection Points </li></ul><ul><ul><li>Industry moving from Windows to the Windows NT platform </li></ul></ul><ul><ul><li>Compiler market moving from Borland (OWL) to the Microsoft C++ Compiler and MFC </li></ul></ul>
  11. 11. ViVi Software’s First Trade Show
  12. 13. 1993- 1994 – ViVi Software <ul><li>ViVi Software is formed </li></ul><ul><ul><li>Alberto Massari and Ivan Pedruzzi join the Team </li></ul></ul><ul><li>Headquartered in… </li></ul><ul><ul><li>A basement in Corso Dogali </li></ul></ul><ul><li>Product Is Re-written in 3 months </li></ul><ul><li>Beta is ready for customers </li></ul><ul><li>Product is presented to Object Design </li></ul><ul><ul><li>Still, no love </li></ul></ul><ul><li>Product is presented to Customers </li></ul><ul><ul><li>Still…. Lot’s of Love!!! </li></ul></ul>
  13. 14. ViVi Software
  14. 15. ViVi Software @ Work
  15. 16. Lessons <ul><li>Take Risks </li></ul><ul><ul><li>Open your “Partita IVA”  </li></ul></ul><ul><li>Talk to Customers!!!! </li></ul><ul><ul><li>And Listen… </li></ul></ul><ul><li>Focus, focus, and… focus </li></ul><ul><ul><li>Cut deep, cut early </li></ul></ul><ul><ul><ul><li>Cut the Schema Design, focus on browsing tool </li></ul></ul></ul><ul><ul><li>Turn down “easy” money, focus on long term vision </li></ul></ul><ul><li>(Re-)Embrace Change </li></ul><ul><ul><li>New platform, new compiler,… </li></ul></ul><ul><li>Don’t be afraid of complete Re-writes </li></ul><ul><li>Work the Network </li></ul><ul><ul><li>Alberto, Ivan… </li></ul></ul><ul><ul><li>Customer leads </li></ul></ul><ul><li>Hire A+ People </li></ul>
  16. 17. ITEA Prize
  17. 18. 1995 <ul><li>Visual Object Manager 1.0 </li></ul><ul><ul><li>Product Ready and Shipping </li></ul></ul><ul><li>Internet for e-Commerce </li></ul><ul><li>The Shrink-wrapping Machine…. </li></ul><ul><li>Marketing, leads, customers </li></ul><ul><ul><li>Worldwide Mailing Campaign </li></ul></ul><ul><li>Near-real Time Technical Support </li></ul>
  18. 19. Lessons <ul><li>The Joy of building products </li></ul><ul><ul><li>There is nothing like shipping products to customers </li></ul></ul><ul><ul><li>… and see them deployed </li></ul></ul><ul><li>Attention to Details </li></ul><ul><li>Believe </li></ul><ul><li>Work hard…really hard </li></ul><ul><ul><li>If it was easy, somebody else would have done it already </li></ul></ul><ul><li>Love and pamper your customers </li></ul>
  19. 20. 1996 The OEM Agreement with Object Design <ul><li>Object Design Management Change </li></ul><ul><ul><li>Bob Goldman </li></ul></ul><ul><li>OEM Agreement is Signed </li></ul><ul><ul><li>The first real money… </li></ul></ul><ul><li>Visual Object Manager become ObjectStore Inspector </li></ul><ul><li>Inspector 2.0, another huge leap forward </li></ul><ul><li>… but… business model not sustainable </li></ul><ul><li>1997: Object Design Buys ViVi Software </li></ul><ul><ul><li>The Negotiation </li></ul></ul><ul><li>1998: ViVi Software goes to Boston </li></ul>
  20. 21. Lessons <ul><li>Always know the value of you company </li></ul><ul><li>If you don’t, let the buyer make the first offer… </li></ul><ul><li>Hire a good lawyer </li></ul><ul><li>Engineers can be good negotiators…  </li></ul><ul><ul><li>Minollo turns tough business man </li></ul></ul>
  21. 22. You Are Here… … now
  22. 23. 1998-2001 The Experience in Boston <ul><li>Risk and Speed </li></ul><ul><ul><li>Fast track promotions </li></ul></ul><ul><li>New Technology and Inflection Points </li></ul><ul><ul><li>The Internet </li></ul></ul><ul><ul><li>XML </li></ul></ul><ul><li>Meeting Adam Bostworth </li></ul><ul><li>Meeting Carl Sjogreen </li></ul><ul><li>NASDAQ at 5200 </li></ul><ul><ul><li>From reality to - easy money and return… </li></ul></ul><ul><li>Workforce Mobility </li></ul>
  23. 24. Lesson Learned Vendi, Guadagna e… Pentiti
  24. 25. You Thought you were going to be here… … but you a really here now
  25. 26. Seattle and Silicon Valley <ul><li>Adam Bosworth Aggressive Recruiting Techniques </li></ul><ul><ul><li>Move to Seattle, then to San Jose, the capital of Silicon Valley </li></ul></ul><ul><li>Join BEA Systems in Seattle </li></ul><ul><ul><li>Build the First Integrated Java Platform …the Visual Basic of Java </li></ul></ul><ul><ul><li>Recruit Carl… again.. </li></ul></ul><ul><li>Adam’s Team </li></ul><ul><ul><li>Tod Nielsen, Rod Chavez, David Bau, Mark Igra, …. </li></ul></ul><ul><ul><li>And the WebLogic Team </li></ul></ul><ul><ul><ul><li>Scott Diezen (the father of J2EE)… </li></ul></ul></ul><ul><li>The Oracle Opportunity </li></ul>
  26. 27. BEA
  27. 28. Oracle
  28. 29. Lesson Learned <ul><li>Work with Great People on Great things </li></ul><ul><ul><li>Title and Money are always secondary </li></ul></ul><ul><li>You have to move where the opportunity is </li></ul><ul><li>Job mobility in IT is a fact of life </li></ul>
  29. 30. Creating Innovative Products The IT World Seen from a Simple Baker’s Eyes
  30. 31. Most high-performance teams are motivated by one thing (primarily)…
  31. 32. Changing the World <ul><li>Define a World… </li></ul>… and change it!!!
  32. 33. Changing the World: Steps <ul><li>Need an Inflection Point </li></ul><ul><ul><li>“ And yet it does move” </li></ul></ul><ul><li>Customer Need </li></ul><ul><li>Idea/Vision </li></ul><ul><ul><li>“ Give me a lever and a fulcrum and I shall move the world ” , Archimedes </li></ul></ul><ul><li>Team </li></ul><ul><ul><li>People who have done it before and… who have NOT done it </li></ul></ul><ul><li>Execution </li></ul><ul><ul><li>Strategy gets you on the playing field, but execution execution pays the bills. “, Gordon Eubanks </li></ul></ul>
  33. 34. The Idea
  34. 35. The Idea <ul><li>Better be a great Idea – D U H ! </li></ul><ul><li>Better be original </li></ul><ul><ul><li>Only big companies can afford building me-too products </li></ul></ul><ul><ul><li>“ look at something people are trying to do, and figure out how to do it in a way that doesn't suck” Paul Graham </li></ul></ul><ul><ul><li>Examples: Google Search, </li></ul></ul><ul><li>Idea Sources </li></ul><ul><ul><li>Customer (careful how you listen to customer, they will make you build yesterday products)‏ </li></ul></ul><ul><ul><li>Engineers </li></ul></ul><ul><ul><li>Business People </li></ul></ul><ul><li>Better be mad about something </li></ul><ul><ul><li>Best idea comes from people mad at something </li></ul></ul>
  35. 36. The Idea <ul><li>Look for disruptive technologies </li></ul><ul><ul><li>Examples: HTTP, Java, Broadband </li></ul></ul><ul><li>Look for disruptive Business Models </li></ul><ul><ul><li>Google Pay-per-click, Software as a service (, virtual Stores (Yahoo stores, eBay, Amazon), Open Source software </li></ul></ul><ul><li>One-Sentence Rule </li></ul><ul><ul><li>You should be able to express a good idea in one sentence </li></ul></ul><ul><li>The KISS Principle </li></ul><ul><ul><li>Keep It Simple and Stupid …or, Keep it Simple, Stupid </li></ul></ul>
  36. 37. Recognize Relevant Cycles: Standardization <ul><li>The Standardization Cycle </li></ul><ul><li>Examples: J2EE, WebServices, BPEL, … </li></ul>
  37. 38. Recognize Relevant Cycles: Tech Cycles <ul><li>Technology Products Tend to go Through Cycles </li></ul><ul><ul><li>E.g. Thick client (Client Server)-Thin client (HTML)-Thick(er) client (AJAX)‏ </li></ul></ul><ul><ul><li>Convergence-divergence: </li></ul></ul><ul><ul><ul><li>Application Development – Application Integration </li></ul></ul></ul><ul><ul><ul><li>Weather-site, Stock Quote Site, Email… - Portals </li></ul></ul></ul><ul><ul><ul><li>Phone-PDA-> Smart Phone </li></ul></ul></ul><ul><ul><ul><li>Phone-Camera->Camera-phone </li></ul></ul></ul><ul><ul><ul><li>Telephony-IT Technology </li></ul></ul></ul><ul><ul><li>Fixed Telephony spinning off Mobile branches and now buying them back </li></ul></ul>
  38. 39. The Team
  39. 40. “ What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people” Paul Graham
  40. 41. Team – Hiring/Interviewing <ul><li>Hire Smart people who Get Things Done </li></ul><ul><li>Have a rigorous interview process that everybody understands and follows </li></ul><ul><ul><li>Define an interview plan, split responsibilities </li></ul></ul><ul><ul><li>Ask tough programming questions to engineers </li></ul></ul><ul><ul><li>Ask situational questions </li></ul></ul><ul><ul><li>Ask impossible questions </li></ul></ul><ul><ul><ul><li>How many gas stations are in Genova? </li></ul></ul></ul><ul><ul><li>Ask technical questions outside the domain </li></ul></ul><ul><ul><ul><li>Design an elevator </li></ul></ul></ul><ul><li>Make sure all relevant people interview the candidate </li></ul><ul><ul><li>The team has to Buy-In the candidate which creates positive environment for candidate to succeed </li></ul></ul><ul><li>Hire for Talent not for Knowledge </li></ul>
  41. 42. Team-Hiring/Interview Remember!!!!! As hire As Bs hire Cs
  42. 43. Team - Hiring <ul><li>If you have even a single doubt-> NO HIRE </li></ul><ul><li>See people 2-3 times before hiring </li></ul><ul><ul><ul><li>You will see the typical personality patterns emerge after the second meeting </li></ul></ul></ul><ul><ul><li>Take people out to dinner before making the offer </li></ul></ul><ul><ul><ul><ul><li>See how they behave in a social environment </li></ul></ul></ul></ul><ul><li>See http:// / </li></ul>
  43. 44. Team-Hiring In many cases you will spend more time with your new hire that with your relevant other…
  44. 45. Team Composition - General <ul><li>Only Hire As </li></ul><ul><ul><li>An A engineer is 10 to  infinite times more productive than a B one </li></ul></ul><ul><li>Build the right culture from the very beginning </li></ul><ul><ul><li>Building a team == baking a cake </li></ul></ul><ul><li>Balance Junior vs. Senior </li></ul><ul><li>Know yourself and your Team </li></ul><ul><ul><li>E.g. Meyer Briggs </li></ul></ul><ul><li>Do you have the right DNA? </li></ul><ul><ul><li>If not, go hire or buy a company </li></ul></ul><ul><ul><li>If you are embarking in a product line extension, definitely buy </li></ul></ul><ul><li>You don’t need big teams to change the world </li></ul><ul><ul><li>8-10 developers can write a lot of code </li></ul></ul>
  45. 46. “ The leaders of Great Groups love talent and know where to find it. They revel in the talent of others .” Warren Bennis & Patricia Ward Biederman, Organizing Genius
  46. 47. “ The leaders of Great Teams, are fanatic, relentless, persistent, aggressive… recruiters”
  47. 48. Why Do We love Freaks? <ul><li>(1) Because when Anything Interesting happens … it was a freak who did it. (Period.) </li></ul><ul><li>(2) Freaks are fun. (Freaks are also a pain.) (Freaks are never boring.) </li></ul><ul><li>(3) We need freaks . Especially in freaky times. (Hint: These are freaky times, for you & me & the CIA & the Army & Avon.) </li></ul><ul><li>(4) A critical mass of freaks-in-our-midst automatically make us-who-are-not-so-freaky at least somewhat more freaky. (Which is a Good Thing in freaky times—see immediately above.) </li></ul><ul><li>(5) Freaks are the only (ONLY) ones who succeed—as in, make it into the history books. </li></ul><ul><li>(6) Freaks keep us from falling into ruts. (If we listen to them.) (We seldom listen to them.) (Which is why most of us—and our organizations—are in ruts. Make that chasms.)‏ </li></ul>
  48. 49. Team - Misc <ul><li>The 5 Fs Principle </li></ul><ul><ul><li>Fun, Fame, Fortune, Family, Force, … </li></ul></ul>
  49. 50. Execution <ul><ul><li>A good plan violently executed now is better than a perfect plan next week.&quot; (General George S. Patton)‏ </li></ul></ul>
  50. 51. Vision-Goals-Metrics <ul><li>You need a compelling Vision and Mission </li></ul><ul><ul><li>Microsoft: 1 computer on every desktop </li></ul></ul><ul><ul><li>GE: Be n.1 or n.2 in every market we play </li></ul></ul><ul><li>Set aggressive Goals </li></ul><ul><ul><li>You only get what you ask for </li></ul></ul><ul><ul><li>Belief-action-results </li></ul></ul><ul><ul><li>A man on the moon within the next 10 years </li></ul></ul><ul><li>Everybody needs to be behind it </li></ul><ul><ul><li>Agree, disagree… commit </li></ul></ul><ul><ul><li>… but listen to the “bastian contrario” routinely </li></ul></ul><ul><ul><li>Re-assess the Vision when appropriate </li></ul></ul><ul><ul><li>Vision, culture and metrics fight politics (cook a good cake)‏ </li></ul></ul><ul><li>Constantly Measure Results Against Goals </li></ul><ul><ul><li>If you don’t measure it you don’t know where you are… …and when you get there </li></ul></ul>
  51. 52. Manage the Vision, Manage Mentor People <ul><li>Map Individual goals to product and corporate vision </li></ul><ul><ul><li>Makes sure everybody knows what is their contribution to the vision </li></ul></ul><ul><li>Don’t promote Great Engineers to management Positions – Define Separate Career Paths </li></ul><ul><ul><li>Unless that’s what they want to do </li></ul></ul><ul><li>Know yourself and know the team </li></ul><ul><ul><li>Myers-Briggs test </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>You CANNOT change people!!!!! </li></ul></ul><ul><li>Establish Measurable goals and personal development plans and review them every 6-12 month </li></ul><ul><ul><li>Measure everybody </li></ul></ul><ul><li>Overcompensate the top performers </li></ul><ul><ul><li>And Routinely Remove the bottom 5% (if applicable)‏ </li></ul></ul>
  52. 53. Vision and Values <ul><li>Define and practice corporate values </li></ul><ul><ul><li>It is an important ingredient of “the cake” </li></ul></ul><ul><ul><ul><li>Respect, Customer Focus, Accountability,… </li></ul></ul></ul><ul><ul><ul><li>Innovation, Integrity, Excellence in Execution, … </li></ul></ul></ul><ul><ul><ul><li>3Ps Promise, “Phollow” through, </li></ul></ul></ul><ul><ul><li>Apply those values in everything you do, starting from beginning, starting from the top </li></ul></ul><ul><ul><ul><li>… or else it is just BS </li></ul></ul></ul><ul><li>E.G. The Value of my Team at Oracle </li></ul><ul><ul><li>“ We care!” </li></ul></ul>
  53. 54. Embrace Change <ul><li>Change is a fact of life and it is a known constant of software development </li></ul>
  54. 55. Embrace change
  55. 56. Team Functions The “One ass to kick” Principle
  56. 57. Management/Founders <ul><li>Technical Innovation Comes From Technical People </li></ul><ul><ul><li>Larry Ellison, Bill Gates, Steve Jobs, Sergei Brin… </li></ul></ul><ul><li>History seems to show that you are better off with a technical people at the elm </li></ul><ul><ul><li>… in technology companies </li></ul></ul>
  57. 58. Team Composition - Functions <ul><li>“ Separate Church and State” AKA in Software as “Separate Product Management and Engineering” </li></ul><ul><ul><li>Keep PM motivated by customer and business drivers </li></ul></ul><ul><ul><li>Keep engineers motivated by: tough problem to solve, quality, performance, punctuality </li></ul></ul><ul><ul><li>Keep Sales people away from your engineers and requirements </li></ul></ul><ul><ul><ul><li>Sales input through product management </li></ul></ul></ul><ul><li>Product Management </li></ul><ul><ul><li>What and why </li></ul></ul><ul><ul><li>Product Design/Doc </li></ul></ul><ul><ul><ul><li>Responsible for user-centered design </li></ul></ul></ul><ul><li>Engineering (QA, Sustained Engineering) </li></ul><ul><ul><li>Responsible for changing the world </li></ul></ul><ul><ul><li>Define “how” and “how long” </li></ul></ul><ul><li>Architecture </li></ul><ul><ul><li>Holds the key to the overall architecture f the product </li></ul></ul>
  58. 59. Team Functions - Continued <ul><li>Business Development </li></ul><ul><ul><li>Develops the business  </li></ul></ul><ul><li>Marketing </li></ul><ul><li>Sales </li></ul><ul><li>Pre-sales </li></ul><ul><li>Consulting </li></ul><ul><li>SWATT Team </li></ul>
  59. 60. The Product Manager Role <ul><li>The CEO of the Product (area) </li></ul><ul><ul><li>Responsible for ALL the user-visible aspect of the product </li></ul></ul><ul><ul><li>User-Focused </li></ul></ul><ul><ul><li>Business Focussed </li></ul></ul><ul><ul><li>First User of the product </li></ul></ul><ul><li>Defines the “What” we build and “Why” </li></ul><ul><ul><li>Defines what NOT to build and why </li></ul></ul><ul><ul><ul><li>PM makes cuts/trade-off </li></ul></ul></ul><ul><ul><li>PMs keep everybody a little unhappy </li></ul></ul><ul><li>Define the product as a whole </li></ul><ul><ul><li>Features, Packaging, Support, Price…. </li></ul></ul><ul><li>Outside Customers: </li></ul><ul><ul><li>The guy who writes the check </li></ul></ul><ul><ul><li>The guy who uses the product </li></ul></ul>
  60. 61. Product Management Team <ul><li>Inside Customers: </li></ul><ul><ul><li>Engineering: Roadmap/Requirements/Use Cases/Cuts/Tradeoff </li></ul></ul><ul><ul><li>Marketing: content-positioning </li></ul></ul><ul><ul><li>Sales: training, pre-sales support </li></ul></ul><ul><ul><li>Channel: Sis/ISVs </li></ul></ul><ul><ul><li>Post-sales escalations </li></ul></ul><ul><li>1 (PM)/6 Developers </li></ul>
  61. 62. Product Designer (AKA Program Manager) Role <ul><li>Program mgmt resides between development and product management… and customers </li></ul><ul><li>First User of the product </li></ul><ul><li>Customers: </li></ul><ul><ul><li>Outside: the user of the product </li></ul></ul><ul><ul><li>Inside: Engineering- Specs… </li></ul></ul><ul><li>Written product specification </li></ul><ul><ul><li>The PD is responsible for writing down the specification. He/she is not responsible for all ideas and all Specs </li></ul></ul><ul><li>Use Case Implementation </li></ul><ul><ul><li>The PD builds prototypes, implements customers use cases and oversees the &quot;usability test&quot; of the features/interfaces </li></ul></ul><ul><li>Ensure consistent User Experience </li></ul><ul><ul><li>API-UI </li></ul></ul>
  62. 63. Product Designer: Tell Me More <ul><li>File Bugs </li></ul><ul><li>All implementation trade-offs </li></ul><ul><ul><li>Fine-grained trade-offs that impact user visible aspects of the product </li></ul></ul><ul><li>Coordination of the product development groups </li></ul><ul><ul><li>outside product group </li></ul></ul><ul><li>Customer Visits (35%)‏ </li></ul><ul><ul><li>In depth technical product presentations to customer </li></ul></ul><ul><ul><li>Functional Specification validation </li></ul></ul><ul><ul><li>Alpha-Beta validation </li></ul></ul><ul><ul><li>Use case gathering </li></ul></ul>
  63. 64. Engineering <ul><li>Architects </li></ul><ul><ul><li>Who take accountability for the architecture? </li></ul></ul><ul><ul><li>The KISS Principle. Keep It Simple, (and) Stupid </li></ul></ul><ul><li>QA </li></ul><ul><ul><li>Depending on the product keep a 1-2 to 2-3 QA/Dev ratio </li></ul></ul><ul><ul><li>Only hire A </li></ul></ul><ul><ul><li>Make QA an engineering problem, avoid delegation </li></ul></ul><ul><li>Performance </li></ul><ul><ul><li>Have performance engineers if you can afford it or make it a developer’s problem </li></ul></ul><ul><ul><li>Measure, measure and measure from the first build on </li></ul></ul><ul><li>Release Management </li></ul><ul><ul><li>Track the details to get the product out the door </li></ul></ul><ul><li>10-1-1 AKA Eat the Dog Food </li></ul><ul><ul><li>Work hard 10 month, take a month off, work one month at a customer site using your product </li></ul></ul>
  64. 65. How We Make Decisions <ul><li>Clear Decision Owner </li></ul><ul><ul><li>One ass to kick </li></ul></ul><ul><li>Publish Time Frame </li></ul><ul><li>Communication </li></ul><ul><li>Agree, Disagree, Commit </li></ul><ul><ul><li>Lead, follow, or get out of the way!!! </li></ul></ul>
  65. 66. Process <ul><li>Idea </li></ul><ul><li>Validate the Idea </li></ul><ul><li>High Level PRD (Product Requirement Document)‏ </li></ul><ul><ul><li>Product Management, involve key engineers/architect </li></ul></ul><ul><li>Build Prototype </li></ul><ul><li>Hit the Road </li></ul><ul><ul><li>Validate high level requirements and prototype with customers </li></ul></ul><ul><li>Implementation: The Old Way: Waterfall </li></ul><ul><ul><ul><li>Specifications </li></ul></ul></ul><ul><ul><ul><ul><li>Don’t write single line of code that does not have a design note behind it </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Get sign off from Architect, PM and Release manager </li></ul></ul></ul></ul><ul><ul><ul><li>Development </li></ul></ul></ul><ul><ul><ul><ul><li>Adopt and enforce one methodology </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Build everyday (multiple times a day)‏ </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Punish who breaks the build </li></ul></ul></ul></ul>
  66. 67. Process the New Way <ul><li>Scrum and Agile Development </li></ul>
  67. 68. Scrums Roles <ul><li>Product Owner </li></ul><ul><ul><li>Defines the backlog, represents customers, prioritizes features </li></ul></ul><ul><ul><li>Role may be filled by PM, Dev Managers, VP depending on “product” definition </li></ul></ul><ul><li>Scrum-Master </li></ul><ul><ul><li>Facilitates the project, identifies and removes impediments </li></ul></ul><ul><ul><li>The “Project Manager” of Scrum </li></ul></ul><ul><ul><li>Does not have seniority or “power” over scrum team </li></ul></ul><ul><li>Project Team </li></ul><ul><ul><li>Development Engineers </li></ul></ul><ul><ul><li>QA Engineers </li></ul></ul><ul><ul><li>Documentation Writers </li></ul></ul><ul><ul><li>Product Managers (who are not product owners)‏ </li></ul></ul>
  68. 69. The Importance of “Doneness” Definition of Done
  69. 70. Process <ul><li>Ramp Down </li></ul><ul><ul><li>Carefully triage the bugs daily to see what gets pushed out </li></ul></ul><ul><li>SHIP </li></ul><ul><li>Get drunk and take a week off </li></ul><ul><li>Work on Service Pack 1 </li></ul>
  70. 71. Conclusions <ul><li>Embrace Change </li></ul><ul><li>Stay Close to, Talk to, Listen to , and Pamper your Customers </li></ul><ul><li>Work Hard, Very Hard </li></ul><ul><ul><li>with Passion </li></ul></ul>
  71. 72. <ul><li>Grafico Nasdaq </li></ul><ul><li>Mentor </li></ul><ul><li>Esempio di Persone Brillanti (David Bau, Indu…)‏ </li></ul><ul><li>Riconoscere I cicli (Thin-thick, Standards, Chasm)‏ </li></ul><ul><li>Stay at the course </li></ul><ul><ul><li>Life is made of tradeoff (examples: ViVi Software, Net4Call,…)‏ </li></ul></ul><ul><li>Multicultural </li></ul><ul><ul><li>Political Correctness and Sexual harassment </li></ul></ul><ul><li>Code Rules </li></ul><ul><li>Talk to customers always (and listen)‏ </li></ul><ul><li>Eat the dog food </li></ul>
  72. 73. Reading Material <ul><li>Developer Productivity </li></ul><ul><ul><li>http:// </li></ul></ul><ul><li>How to start a company </li></ul><ul><ul><li> </li></ul></ul><ul><li>Adam Bostworth Blog </li></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Kiss Principle </li></ul></ul>
  73. 74. Backup Slides
  74. 75. <ul><li>1. Cultivate & reward creativity. 2. Invest in the creative ecosystem. 3. Embrace diversity. 4. Nurture the creatives. 5. Value risk-taking. 6. Be authentic (emphasize uniqueness) 7. Invest in and build on quality of place. 8. Remove barriers to creativity. 9. Take responsibility for change. Development as D.I.Y. 10. Ensure that every person, especially children, has the right to creativity. Become a “Steward of creativity.” * 2003/The Creative 100/Memphis Source: Richard Florida, The Rise of the Creative Class </li></ul>The Memphis Manifesto* Building a Community of Ideas
  75. 76. Kevin Roberts’ Credo <ul><li>1 . Ready. Fire! Aim. 2. If it ain’t broke ... Break it! 3. Hire crazies. 4. Ask dumb questions. 5. Pursue failure. 6. Lead, follow ... or get out of the way! 7. Spread confusion. 8. Ditch your office. 9. Read odd stuff. 10. Avoid moderation ! </li></ul>
  76. 77. Interview <ul><li>Pay a contractor for 7 days with one piece of gold and 2 straight cuts </li></ul><ul><li>One bicycle rider </li></ul><ul><li>Two Containers </li></ul><ul><li>10 Bags of balls </li></ul><ul><li>3 bag, wrong label. Pick one ball </li></ul><ul><li>Weight 9 Balls </li></ul><ul><li>Weight 12 Balls </li></ul><ul><li>3 lights bulbs </li></ul><ul><li>4 man, 1,2,5,10 </li></ul><ul><li>Gas Station </li></ul>