Common use of Development Schedule Clause in Contracts

Development Schedule. Below are the key milestone dates that the Parties commit to meet for the M2 project. Sharp shall manage and be responsible for the development, testing and production schedules for the M2 hardware. Danger shall manage and be responsible for the development and testing schedules for the M2 software. The parties shall collaborate and share scheduling information. [ * ] Milestones for T-Mobile USA [ * ] Sharp ships out ([ * ]) EVT0 units to Danger [ * ] Sharp ships out ([ * ]) EVT 1 units to Danger [ * ] Software Feature Complete (Danger) [ * ] Sharp ships out ([ * ]) EVT2 units to Danger [ * ] Sharp ships out ([ * ]) DVT1 units to Danger [ * ] Alpha OS software available (Danger) [ * ] Sharp ships out ([ * ])PVT units to Danger [ * ] Beta OS software available (Danger) [ * ] (RC) Release Candidate OS software available (Danger) [ * ] (RC) Release Candidate OS #0 software available (Danger) [ * ] (RC) Release Candidate OS #1 software available (Danger) [ * ] (RC) Release Candidate OS (final) software available (Danger) [ * ] Sharp submits final units to T-Mobile for testing [ * ] [ * ] approves M2 hardware (proceed with production start) [ * ] Sharp ships out ([ * ]) Pre-Production Unit to Danger [ * ] [ * ] approves M2 software and issues Terminal Approval (TA) [ * ] Sharp ships initial [ * ] units to [ * ] distribution center [ * ] Commercial Launch of M2 by [ * ]

Development Schedule. Below are the key milestone dates that the Parties commit to meet for the M2 S1 project. Sharp shall manage and be responsible for the development, testing and production schedules for the M2 S1 hardware. Danger shall manage and be responsible for the development and testing schedules for the M2 S1 software. The parties shall collaborate and share scheduling information. [ * [*] Milestones for T-Mobile USA = Certain confidential information contained in this document, marked by brackets, has been omitted and filed separately with the Securities and Exchange Commission pursuant to Rule 406 of the Securities Act of 1933, as amended. [ * ] Sharp ships out ([ * ]) EVT0 EVT1 units to Danger [ * ] Sharp ships out ([ * ]) EVT 1 units to Danger [ * ] Software Feature Complete (Danger) [ * ] Sharp ships out ([ * ]) EVT2 DVT0 units to Danger [ * ] Sharp ships out ([ * ]) DVT1 units to Danger [ * ] [ * ] delivers candidate radio firmware to Danger [ * ] Sharp ships ([ * ]) early PVT0 units for memory testing to Danger [ * ] Sharp ships out ([ * ])PVT0 units to Danger [ * ] Software Feature Complete declare (Danger) [ * ] Final Candidate Firmware from [ * ] delivered to Sharp & Danger [ * ] Alpha OS software available declare (Danger) [ * ] Sharp ships out ([ * ])PVT ) PVT2 units to Danger [ * ] Beta OS software available declare (Danger) [ * ] (RC) Release Candidate OS software available (Danger) [ * ] (RC) Release Candidate OS #0 software available (Danger) [ * ] (RC) Release Candidate OS #1 software available (Danger) [ * ] (RC) Release Candidate OS (final) software available Factory Package to be delivered to Sharp (Danger) [ * ] Sharp submits final units to T-Mobile for testing [ * ] [ * ] approves M2 S1 hardware (proceed with production start) [ * ] Sharp ships out ([ * ]) Pre-Production Unit to Danger [ * ] [ * ] approves M2 S1 software and issues Terminal Approval (TA) [ * ] Sharp ships initial [ * ] units to [ * ] distribution center [ * ] Commercial Launch of M2 S1 by [ * ]

Development Schedule. Below are the key milestone dates that the Parties commit to meet for the M2 SHURIKEN project. Sharp shall manage and be responsible for the development, testing and production schedules for the M2 SHURIKEN hardware. Danger shall manage and be responsible for the development and testing schedules for the M2 SHURIKEN software. The parties shall collaborate and share scheduling information. [ * ] Milestones for T-Mobile USA Sharp ships out ([ * ]) EVT2 to Danger w/Sharp USB charging rework [ * ] Sharp ships out ([ * ]) EVT0 EVT3 PCB units to Danger [ * ] Sharp ships out ([ * ]) EVT 1 units to Danger [ * ] Software Feature Complete (DangerEVT3(Navi-style) [ * ] Sharp ships out ([ * ]) EVT2 units to Danger [ * ] Sharp ships out ([ * ]) DVT1 units EVT3 handmade cabinet unit to Danger [ * ] Software Feature Complete declared on EVT2 (except mood lights) [ * ] Software Alpha OS software available (Danger) declared on DVT [ * ] Sharp ships out ([ * ])PVT units ) DVT1 to Danger [ * ] Beta OS software available (Danger) [ * ] (RC) Release Candidate OS software available (Danger) [ * ] (RC) Release Candidate OS #0 software available (Danger) [ * ] (RC) Release Candidate OS #1 software available (Danger) [ * ] (RC) Release Candidate OS (final) software available (Danger) [ * ] Sharp submits final units to T-Mobile for testing [ * ] [ * ] approves M2 hardware (proceed with production start) [ * ] Sharp ships out ([ * ]) Pre-Production Unit PVT1 units to Danger [ * ] Sharp ships out ([ * ]) PVT2 units to Danger [ * ] Software Beta declared on PVT1 [ * ] Software Release for Test Cycle 1 [ * ] Software Release Candidate for Test Cycle 2 [ * ] Software Release for Test Cycle 3 and Factory Package delivered to Sharp [ * ] Sharp ships out ([ * ]) PP units to Danger [ * ] Sharp submits final units to [ * ] for testing [ * ] [ * ] approves M2 Shuriken hardware (proceed with production start) [ * ] [ * ] approves Shuriken software and issues Terminal Approval (TA) [ * ] Mass Production starts [ * ] Sharp ships initial [ * ] units to [ * ] T-Mobile distribution center [ * ] Commercial Launch of M2 Shuriken by [ * ]

Development Schedule. Below are the key milestone dates that the Parties commit to meet for the M2 project. Sharp shall manage and be responsible for the development, testing and production schedules for the M2 hardware. Danger shall manage and be responsible for the development and testing schedules for the M2 software. The parties shall collaborate and share scheduling information. [ * ] Milestones for T-Mobile USA [ * ] Sharp ships out ([ * ]) EVT0 units to Danger [ * ] Sharp ships out ([ * ]) EVT 1 units to Danger [ * ] Software Feature Complete (Danger) [ * ] Sharp ships out ([ * ]) EVT2 units to Danger [ * ] Sharp ships out ([ * ]) DVT1 units to Danger [ * ] Alpha OS software available (Danger) [ * ] Sharp ships out ([ * ])PVT units to Danger [ * ] Beta OS software available (Danger) [ * ] (RC) Release Candidate OS software available (Danger) [ * ] (RC) Release Candidate OS #0 software available (Danger) [ * ] (RC) Release Candidate OS #1 software available (Danger) [ * ] (RC) Release Candidate OS (final) software available (Danger) [ * ] Sharp submits final units to T-Mobile for testing [ * ] [ * ] approves M2 hardware (proceed with production start) [ * ] Sharp ships out ([ * ]) Pre-Production Unit to Danger [ * ] [ * ] approves M2 software and issues Terminal Approval (TA) [ * ] Sharp ships initial [ * ] units to [ * ] distribution center [ * ] Commercial Launch of M2 by [ * ]

Development Schedule. Below are the key milestone dates that the Parties commit to meet for the M2 SHURIKEN project. Sharp shall manage and be responsible for the development, testing and production schedules for the M2 SHURIKEN hardware. Danger shall manage and be responsible for the development and testing schedules for the M2 SHURIKEN software. The parties shall collaborate and share scheduling information. [ * ] Date Milestones for T-Mobile USA [ * ] Sharp ships out ([ * ]) EVT0 EVT2 to Danger w/Sharp USB charging rework [ * ] Sharp ships out ([ * ]) EVT3 PCB units to Danger [ * ] Sharp ships out ([ * ]) EVT 1 units to Danger [ * ] Software Feature Complete (DangerEVT3(Navi-style) [ * ] Sharp ships out ([ * ]) EVT2 units to Danger [ * ] Sharp ships out ([ * ]) DVT1 units EVT3 handmade cabinet unit to Danger [ * ] Software Feature Complete declared on EVT2 (except mood lights) [ * ] Software Alpha OS software available (Danger) declared on DVT [ * ] Sharp ships out ([ * ])PVT units ) DVT1 to Danger [ * ] Beta OS software available (Danger) [ * ] (RC) Release Candidate OS software available (Danger) [ * ] (RC) Release Candidate OS #0 software available (Danger) [ * ] (RC) Release Candidate OS #1 software available (Danger) [ * ] (RC) Release Candidate OS (final) software available (Danger) [ * ] Sharp submits final units to T-Mobile for testing [ * ] [ * ] approves M2 hardware (proceed with production start) [ * ] Sharp ships out ([ * ]) Pre-Production Unit PVT1 units to Danger [ * ] Sharp ships out ([ * ]) PVT2 units to Danger [ * ] Software Beta declared on PVT1 [ * ] Software Release for Test Cycle 1 [ * ] Software Release Candidate for Test Cycle 2 [ * ] Software Release for Test Cycle 3 and Factory Package delivered to Sharp [ * ] Sharp ships out ([ * ]) PP units to Danger [ * ] Sharp submits final units to [ * ] for testing [ * ] [ * ] approves M2 Shuriken hardware (proceed with production start) [ * ] [ * ] approves Shuriken software and issues Terminal Approval (TA) [ * ] Mass Production starts [ * ] Sharp ships initial [ * ] units to [ * ] T-Mobile distribution center [ * ] Commercial Launch of M2 Shuriken by [ * ]