1 / 23

Delivering World Class Software

Delivering World Class Software. Jeffrey Murray Test Manager PowerPoint Microsoft Silicon Valley. Goals for today. Microsoft Silicon Valley . Over 1800 employees, plus 400 vendors/contractors. Approx. 450 employees in San Francisco. Jeffrey Murray … What’s my job?.

fausto
Download Presentation

Delivering World Class Software

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. Delivering World Class Software Jeffrey MurrayTest Manager PowerPoint Microsoft Silicon Valley

  2. Goals for today

  3. Microsoft Silicon Valley • Over 1800 employees, plus 400 vendors/contractors. Approx. 450 employees in San Francisco.

  4. Jeffrey Murray … What’s my job?

  5. The Office Product Cycle About every 3 years a major release of Office comes out with features aimed at increasing productivity and ease of use for our customers.

  6. What is Office 2010? Online Online Online Online

  7. How many people does it take to ship core Office?

  8. Project Management

  9. Plan new features New ribbon Better graphics Animation painter On line editing Projector setup Save to video New animation timeline Single Document interface SlideShow broadcast Co-authoring New transitions Better animations Sections Native video support Split video Camera integration Hardware support ODF support • What is the vision for the product? • Make lists of features you want to do, listen to customers, and see what is possible • Estimate and prioritize what is you can do in the time you have • Triage these until you can fit the schedule • Then write page 1 specs and go to step 3

  10. Code the features! • Feature team makes the decisions • Must fit into allowed development time • Must be fully resourced • Responsible for getting it done • Management will approve features via • Adds/Cuts • Product priorities and opportunities • Manage risk • 8 questions

  11. Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew Feature crew

  12. Typical 28 to 32 month schedule 8 months: Design and implement Unit test and validate 8 questions 4 Months Beta 1 about 10,000 users Beta 2 about 1,000,000 users Planning Phase 4-6 months Create lists and 1 page specs Development and test estimate and risk assessment Adds/cuts 12 months Planned testing phase, validation, user scenarios, international, stress, security, configuration, accessibility, compatibility etc. 4 Months Features ready to go Fix last remaining important bugs

  13. Important checkpoints No coding without dev/test/pm resource Code complete: no changes without a bug entered Triage teams in place Feature demo and 8 questions answered Product must be internally dogfoodable All metrics and goals must be met

  14. Metrics and Quality • Good planning is the key to good quality • “If you fail to plan you plan to fail” • Features added or changed late are always more buggy and risky • Proper design, test, automation support produces better code • Bug rates are good way to track quality all else being equal • Customer feedback through Watson

  15. Typical Office Product Bug Trend

  16. What makes it work! • Checks and balances • Testing signs off on specs • Dev signs of on test plans • PM charged with overseeing progress of dev/test

  17. What makes it work? (continued) • Constant and never ending improvement • Test involved earlier • Automation • Technical innovations • Auto code review • Automation validation before release to testers • Listening to customers and competition

  18. Watson We don’t have user steps or data We know what line of code caused the crash and can often guard against it

  19. Questions about the Office Cycle?

  20. Microsoft wants you if?

  21. Career Tips • Companies are better at identifying talent within you than you are at bluffing your way through an interview. Make sure you are there for the right reasons and don’t hold back. • Don’t plan your whole career all at once, you will miss out on interesting opportunities • High tech companies need fresh idea, and that is a great open door for you • You are a professional, act like it • When you screw up (and you will) what you do next is critical • Ask yourself each week, what do I like about my job? • Interview the company beyond the job, a good part of your life will be spent there.

  22. Stories • How I got my Job at Microsoft • Copy protection • Steve’s laptop • OneNote • Office pranks • Elevator • Beach • Peanuts • Disco • balloons

  23. www.microsoft.com/collegewww.viewmyworld.com

More Related