1 / 6

{Your Co. Name}

Please use this slide deck as a starting point for your presentation. You don’t have to use these slides, but keep in mind: We’re budgeting ~15 min per group -- please be concise. The idea is to take detailed discussions off-line.

danae
Download Presentation

{Your Co. Name}

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Please use this slide deck as a starting point for your presentation. You don’t have to use these slides, but keep in mind: • We’re budgeting ~15 min per group -- please be concise. • The idea is to take detailed discussions off-line. • Your slides will be concatenated with everyone else’s, with printed handouts at meeting (please avoid fiddling with the master template) • The bottom line is to focus on interesting -- what experiences (good or bad) would other teams benefit from hearing about? • Thanks! • -andy <andy@payne.org> Confidential

  2. {Your Co. Name} {logo} • We’re building a new generation anti-gravity system, powered entirely with MountainDew and feed corn. • Site launched in Feb ‘06 • 2 yrs old, $500b in funding (CRV + GC), 150K employees Please make sure all attendees are listed. Please note in your email to me the citizenship of any non-US citizens (needed for BBN). Some suggested content to cover; feel free to add items. Avoid content-free marketing speak. Confidential

  3. {Your Co. Name} (Optional) Screenshot If it’s easier to “show” than “tell”, a screenshot may be helpful. Confidential

  4. {Your Co. Name} Technology Architecture Ideally, provide a picture. Note that embedded Visio objects may not render properly. Cover the items that you think others would be interested in, with an emphasis on anything special or unique about what you’re doing. Suggestions: Stack: OS, app server, database, libraries, third party toolkits, content management system, AJAX libraries, etc. Key packaged apps (if any) Dev env: Dev language(s), unit testing, IDE, version control, bug tracking, automated builds, dev methodology (e.g. XP, Agile), etc. Confidential

  5. {Your Co. Name} Deployment/Ops Architecture Ideally, provide a picture (you probably already have one) Again, cover the interesting items, with an emphasis special/unique. Suggestions: Server “farm”: deployment picture, showing allocation of functions (e.g. app server, db, etc.), load balancing, firewall Storage: size, configuration (e.g. local RAID, SAN, etc.), backups Hosting: co-lo vs managed, hosting provider, SLAs, SLA experience (oops), disaster recovery CapEx: leasing vs purchase Confidential

  6. The idea here is “lessons learned”, both good and bad. What experiences have you had that other CTOs would be interested in? {Your Co. Name} • Things that have worked out well: • The Yahoo widget library is great! • Python has been hugely productive. • …and not so well: • The XYZZY library was unstable; we had to yank it out after we went live. • BoBoob went dark for ~3 days, in spite of their SLA. • Feed corn doesn’t taste so good. Just a suggested format. Confidential

More Related