Internal developer tools and bug tracking Arabic / Hebrew Windows 3.1Win95 Japanese Word, OneNote, Outlook

SkyDrive Word Excel PowerPoint

H i r i n g g r e a t p e o p l e f o r t h e r i g h t r o l e People and Roles Guiding principals for the release Vision What the features will do Specifications Implement the features Feature crews Forcing function Milestone

It begins with great people in 3 specific roles Program Manager: Design new features based on customer feedback, Office strategy, and priorities Software Design Engineer: Code the features to specifications, creatively solving design issues and fixing bugs Software Design Engineer in Test: Validate the code, improve the user experience, and deliver a quality product to customers

Vision Collect Input PillarsBig bets Planning memo Step 1 Input Customer focus groups Enterprise engagements Product support list Competitive products Traditional and new Industry direction Software + Services Company objectives Win 8, IE, Windows Live etc.

Now go write a spec Justification User Scenario Goals and non goals Design specifics Details, details, details Pictures Algorithms API definitions Workflows Security Privacy World readiness Performance Responsiveness Accessibility Supportability compatibility

Lifecycle of a feature spec Begins its life as an idea Turns into a 1 page spec Approved by management to be flushed out Dev/Test/PM resources assigned, increases to pages Management approved for coding Spec grows to pages Feature crew takes over and completes it on time Feature crew review and check-in 200 ideas100 approved 60 approved 50 completed

A feature crew’s goal.. “To check in” 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 Feature progress Bug count 8 questions 1 Dev1 Test1 pm Feature Crew

Typical 28 to 32 month schedule Plan Cod e Test Bet a RTM 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 Beta 1 about 10,000 users Beta 2 about 1,000,000 users 12 months Planned testing phase, validation, user scenarios, international, stress, security, configuration, accessibility, compatibility etc. 8 months: Feature crew work broken up into 3 milestones

Metrics and Quality Bug severity, incoming rate, regression rate Writing code – bug count goes up Integration – bug count goes down Automation, Code coverage, security reviews, “uptime” and Dr. Watson! Beta feedback, internal deployment, IT signoff Key partner signoff “TAP” program Test signoff and checklists

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

The future of Office in the cloud Take your existing workflow and extend it to the cloud (backups, collaboration, roaming) Feature updates made easy and administered from one place A more connected and social experience

Core values for Microsoft Microsoft Drive for results Honesty and integrity Big challenges Passion

Career and Interview Tips  Companies can quickly determine if you are wasting their time, don’t waste yours!  Companies want bright and energetic people who are eager to learn. We can always teach you what you need  Interview the company beyond the job, a good part of your life will be there  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?  Realize that although we (companies) may seem arrogant, we need YOU to survive

Stories  How I got my Job at Microsoft  Copy protection  Steve’s laptop  OneNote  Back stage with Steve B  Office pranks  Elevator  Beach  Peanuts  Disco  balloons

Thank you