HW7

!   !   !   !   !  

! 

!   !  

!  

The  Office  Product  Cycle  

About  every  3  years  a  major  release  of  Office   comes  out  with  features  aimed  at  increasing  

produc?vity  and  ease  of  use  for  our  customers.  

What  is  Office?  

How  many  people  does  it  take   to  ship  core  Office?    

800  SoHware  Design  Engineers  (Developers)  

800  SoHware  Design  Engineers  in  Test  (Testers)  

400  Program  Managers  (Feature  designers)  

200  Localizers,  Lab  Managers,  etc.  

200  Planners,  Recruiters,  Sales  and  Marke?ng  

2400  Total  

Customer   feedback  

Office  vision   pillars  

Code   features    

Beta   feedback  

Release   soHware  

It  begins  with  3  dis?nct  roles   •  Program  Manager:  Design  new  features  based  on  

customer  feedback,  Office  strategy,  and  priori?es   •  SoHware  Design  Engineer:  Code  the  features  to  

specifica?ons,  crea?vely  solving  design  issues  and  fixing   bugs  

•  SoHware  Design  Engineer  in  Test:  Validate  the  code,   improve  the  user  experience,  and  deliver  a  quality   product  to  customers  

And  a  spec…  

Walking  the  fine  line  of  a  feature   specifica?on  

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  10-­‐15  

pages  

Management   approved  for  

coding  

Spec  grows  to   30-­‐50  pages  

Feature  crew  takes   over  and  completes  

it  on  ?me    

Feature  crew   review  and  check-­‐in  

A  feature  crew’s  goal  ..  “To  check    in”  

•  Feature  team  makes  the  decisions   –  Must  fit  into  allowed  development  ?me   –  Must  be  fully  resourced   –  Responsible  for  geeng  it  done  

•  Management  will  approve  features  via     –  Adds/Cuts   –  Feature  progress   –  Bug  count   –  8  ques?ons  

1  Dev   1  Test   1  pm   Feature   Crew  

What  is  in  a  feature  specifica?on?   •  Jus?fica?on     •  User  Scenario   •  Goals  and  non  goals   •  Design  specifics   •  Details,  details,  details  

•  Pictures   •  Algorithms   •  API  defini?ons   •  Workflows   •  Security   •  Privacy   •  World  readiness   •  Performance   •  Responsiveness   •  Accessibility   •  Supportability   •  compa?bility  

Typical  28  to  32  month  schedule  

Plan  

Code  

Test  

Beta  

RTM  

Planning  Phase  4-­‐6  months   Create  lists  and  1  page  specs  

Development  and  test  es<mate  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  tes<ng  phase,  valida<on,  user  scenarios,  

interna<onal,  stress,  security,  configura<on,  accessibility,   compa<bility  etc.  

8  months:  Feature  crew  work  broken   up  into  3  milestones  

Metrics  and  Quality   •  Bug  severity,  incoming  rate,  regression  rate   •  Automa?on,  Code  coverage,  security  reviews,   “up?me”  and  Dr.  Watson!  

•  Beta  feedback,  internal  deployment,  IT  signoff   •  Key  partner  signoff  “TAP”  program   •  Test  signoff  and  checklists  

0  

100,000  

200,000  

300,000  

400,000  

500,000  

1   3   5   7   9   11  13  15  17  19  21  23  25  27  29  31  33  35  37  39  41  43  45  47  49  

H it s  

Bucket  number  

Example  Watson  Curve  

Watson  

We  don’t  have  user  steps  or  data   We  know  what  line  of  code  

caused  the  crash  and  can   oHen  guard  against  it  

The  future  of  Office  in  the  cloud   •  Take  your  exis?ng  workflow  and  extend  it  to   the  cloud  (backups,  collabora?on,  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   Office pranks

  Elevator   Beach   Peanuts   Disco   balloons

Thank you