1. Jeffrey Murray Test Manager PowerPoint Microsoft Silicon Valley

2. The parts of the Office Product Cycle Measurements and quality Who Microsoft hires Stories

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

4. Graduated from SUNY Albany Write code Manage people Manage products

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

7. 800 Software Design Engineers (Developers)800 Software Test Engineers (Testers)400 Program Managers (Feature designers)200 Localizers, Lab Managers, etc.200 Planners, Recruiters, Sales and Marketing2400 Total

8. Schedule How much time do we have? Resources Who are they and how many? Features What are you going to do and how risky is it?

9. 1.What is the vision for the product? 2.Make lists of features you want to do, listen to customers, and see what is possible 3.Estimate and prioritize what is you can do in the time you have 4.Triage these until you can fit the schedule 5.Then write page 1 specs and go to step 3 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

10. 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 1 Developer 1 Tester 1 Program Manager Feature team

11. Feature crew

12. 12 months Planned testing phase, validation, user scenarios, international, stress, security, configuration, accessibility, compatibility etc. 12 months Planned testing phase, validation, user scenarios, international, stress, security, configuration, accessibility, compatibility etc. Plan Code Test Beta RTM Planning Phase 4-6 months Create lists and 1 page specs Development and test estimate and risk assessment Adds/cuts Planning Phase 4-6 months Create lists and 1 page specs Development and test estimate and risk assessment Adds/cuts 4 Months Features ready to go Fix last remaining important bugs 4 Months Features ready to go Fix last remaining important bugs 8 months: Design and implement Unit test and validate 8 questions 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 4 Months Beta 1 about 10,000 users Beta 2 about 1,000,000 users

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

14. 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. Checks and balances Testing signs off on specs Dev signs of on test plans PM charged with overseeing progress of dev/test

17. 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. We don’t have user steps or data We know what line of code caused the crash and can often guard against it

20. Microsoft TechnicalPassionPotentialImpact

21. 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. How I got my Job at Microsoft Copy protection Steve’s laptop OneNote Office pranks Elevator Beach Peanuts Disco balloons