1. -0- EVR1, I Sing the Body Electronic, Sep/9/2005 EVR presentation External Viewpoints Reports (EVRs) Hyundai team Sep. 09. 2005 I Sing the Body Electronic A Year with Microsoft on the Multimedia Frontier

2. -1- EVR1, I Sing the Body Electronic, Sep/9/2005 EVRs – I Sing the Body Electronic Contents –Brief description –Atmosphere in Microsoft –Requirement issues –Disharmony between designers and developments –What’s interesting for the Studio project –Q&A

3. -2- EVR1, I Sing the Body Electronic, Sep/9/2005 EVRs – I Sing the Body Electronic Brief description –Illustration of the feud between development members while developing the project –A Multimedia project, Explodapedia (Code name Sendak), is introduced –Hardly begins, hardly ends, but success in the market Typical Microsoft project in 1990s –Main disharmony is caused by Ever changing design requirement Huge gap in the attribute of work and thinking between designers and developers Strong pressure from Gates Young and new leaders as well as project members No appropriate development tools Replacement of leaders Primitive development process

4. -3- EVR1, I Sing the Body Electronic, Sep/9/2005 EVRs – I Sing the Body Electronic Atmosphere in Microsoft –Members are young: The eldest is 30 High capability but not used to Microsoft culture –Small and freewheeling team –Designer Mostly women and new comers Design the external and visible features (e.g. characters, button, shape of window…) Delivers the design requirement to developers –Developer Mostly men Main task is coding and implementation of requirement given by designers –Bill meeting Very demanding Employees start to prepare the meeting 4~6 weeks in advance Gate’s concern

5. -4- EVR1, I Sing the Body Electronic, Sep/9/2005 EVRs – I Sing the Body Electronic Requirement issues –Typical Microsoft strategy and problem New product for new market Impossible to predict: Neither basis nor experience exists Insufficient design requirement –Challenging design matter Multimedia & graphic work The more multimedia feature, the larger disk space –Change requirement Gate’s concern: Not only business scope but design scope External features are easily pointed out for change  Ever changing requirement change

6. -5- EVR1, I Sing the Body Electronic, Sep/9/2005 EVRs – I Sing the Body Electronic Disharmony between designers and developers –Client vs. Supplier relationship Designers build the requirement Developers implement the requirement –No understanding to each other Designers vs. Developers: Different scope and interest –Intrinsic confliction Designers: Vivid graphics to capture the user’s sight Developers: Translate it into hundreds or thousands lines of code –Episode: Sbutton Designer wanted to have button shape to give different look. Not provided by standard window button Caused hundreds of new code over several weeks

7. -6- EVR1, I Sing the Body Electronic, Sep/9/2005 EVRs – I Sing the Body Electronic What’s interesting for Studio project –Requirement analysis Poor requirement always causes unexpected problems E.g. Bad planning –Requirement freeze Early requirement freeze is strongly recommended –Requirement change & management Where we are? Ask “is this function a have-to-have?” –Communication with stakeholders Different scope and interest Need understanding and consideration

8. -7- EVR1, I Sing the Body Electronic, Sep/9/2005 EVRs – I Sing the Body Electronic Q & A