1 / 21

Quality Engineering in Microsoft Office

Quality Engineering in Microsoft Office. Jeffrey Murray Test Manager PowerPoint, Microsoft Silicon Valley. Microsoft Silicon Valley . Over 1600 employees, plus 400 vendors/contractors. Approx 450 employees in San Francisco. Teams on campus: Microsoft Research Windows Live Operations

garvey
Download Presentation

Quality Engineering in Microsoft Office

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. Quality Engineering in Microsoft Office Jeffrey MurrayTest Manager PowerPoint, Microsoft Silicon Valley

  2. Microsoft Silicon Valley • Over 1600 employees, plus 400 vendors/contractors. Approx 450 employees in San Francisco. • Teams on campus: • Microsoft Research • Windows Live Operations • Live Search Labs • MSTV/IPTV/Mediaroom • Tellme • MSN Mobile • MSN Video • Xbox Hardware • Hotmail • MacBU • PowerPoint

  3. Goals for today • Learn about the Office product cycle • Career Tips • Fun Stories

  4. About Me

  5. What Challenges face Office?

  6. Office Challenges

  7. Basic Project Management Variables • Time • How much time do we have? • Resources • Who are they and how many? • Scope • What are you going to do and how risky is it?

  8. The Cast

  9. Scope – What Features? • Feature team makes the decisions • Must align with Office “Pillars” • Must fit into allowed development time • Must be fully resourced • Management will approve features via • Adds/Cuts • Product priorities and opportunities • Manage risk

  10. Office Schedule is fixed to 28-32 Months

  11. Overlapping for Efficiency Milestone 1 Milestone 2

  12. Quality Engineering 1990-1993

  13. Testing grows up ~1993-2000

  14. Pushing Quality Further Upstream 2000+ • Testers involved in spec and design phase • Feature not “checked in” till beta quality • More formal review of test/dev collateral • Code reviews earlier in product cycle • Advancement in dev tools and auto validation programs

  15. When are you ready to ship? Automation Performance Accessibility International Localization Planned testing Stress User Scenarios Backward compatibility Configuration Interoperability Political sensitivity UA approval Visual Freeze Programmability Printing Setup and Upgrade Code Optimization Logo • Your set of risky features need to be under control • Statisticsand trends are all doing the right thing • Checklists • Bug Charts • Dogfood • Watson • Beta feedback • “Show Stopper” • Triage committee

  16. Typical Office Product Bug Trend

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

  18. Career Tips • Companies are better at identifying talent within you than you are at picking the best company. Make sure you don’t hold back at an interview. • Don’t plan your whole career all at once, you will miss out on interesting opportunities • Use that open door • 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 there.

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

  20. Thank you ! www.microsoft.com/collegewww.viewmyworld.com

More Related